New blog domain: kula.blog

By K -
It's still work in progress but new posts will be published on  https://kula.blog/ Thanks to 11ty base blog RSS is working from the start so it should be easy to add to your reader if you still use any :) If now then I hope you can sign up to the newsletter where I'll be publishing new posts and interesting articles to it from time to time. Please use  kula.blog  from now on.
Post a Comment

Book Review: Mastery by Robert Greene

By K -


One idea from Creativity Inc. was with me most of the time I was reading Mastery. Notice advices that are general and make sense the moment you hear them. There is a good chance that they are useless.

I have also heard a term TBU which means True, But Useless that is connected somehow to being more critical about general ideas and advices.

In my opinion, there is a reason why I was thinking about them so much while reading. Stories of master are really interesting and most of them are inspiring but advises that you get sound good but it is really hard to decide what to do with them.

Book is strongly influenced by 10k hours of deliberate practice rule, but I am not so sure if it really is true.
There is an interesting article that can give you more context how this 10k hours rule is just average and you can learn things faster or longer http://www.slate.com/articles/health_and_science/science/2014/09/malcolm_gladwell_s_10_000_hour_rule_for_deliberate_practice_is_wrong_genes.single.html. On the other hand, I have found also critic of the slate article: https://computinged.wordpress.com/2014/10/13/the-10k-rule-stands-deliberate-practice-leads-to-expertise-and-teaching-can-trump-genetics/ that tries to emphasise teaching over genetics.

No matter how you look at it, there are things we like more. Lessons at school we prefer. This might be math, language or music, but we all have some kind of preference. Maybe it is wise to focus on the things that probably would take us less time to master than the one that are really hard?

There is a strong preference of the author for an idea of Universal Man, man of a renaissance that masters various skills such as Leonardo da Vinci who was both scientist and artist. On the other hand, fact is that it is getting harder and harder to accomplish anything substantial in sciences. Nobel prize winners are getting older with time. Most obvious reason for that you have to learn much more to get to the frontier of research. How in this context can you master additional sciences when the first one takes you 20-30 years?

On the other hand from Learning how to Learn I know the idea of chunking. Basically the more you know, the easier it is to learn new things on top of that. Having vast interests also helps our brain create new connections. Learning to play a music instrument or new foreign language can help you with your research in your main field.
On the other hand, I found http://abetterlife.quora.com/If-you-want-to-follow-your-dreams-you-have-to-say-no-to-all-the-alternatives really inspiring and worth thinking about. Main idea is that if we have many interests then we are going to be shaped by circumstances and not by us. However, even Oliver Emberton agrees that you have different contexts in your life. For example exercising is one of those things that you should not ignore no matter how much you should/want to focus on one thing.  Another such skill for me would be English language. No matter how much I would want to focus only on programming, for example, there is only so much, technical expertise alone can give you.

It took me a really long time to finish Mastery. In the meantime, I have finished Coursera: Learning how to Learn and read a lot of articles in Pocket. All of those ideas are interconnected now so it is hard for me to talk only about one thing.

So shortly about the book itself. Language and style are rather boring. Stories are, of course, the best part of the book. Some of them are inspiring, some of them are more like warnings what not to do.

Rating: 4/10

Comments

Post a Comment

Comments:

Popular posts from this blog

How to use NPM packages from private repositories on bitbucket

By K -
Image
Using Node.js you want to use NPM packages for reusable parts of the apps you create, that is a common sense. At the same time not everything makes sense as a public module unfortunately. Right now we are using Bitbucket at work for private repositories but there is a problem. How to use them as NPM modules? We do not want to publish them to the public npmjs.org but still want to have an ability to install them easily. After googling and experimenting I have found simple solution. First create new user in your organization with obscure password and give it read access to the repo. It is best to assign really obscure password but do not fool yourself. This is convenient but you must sacrifice security a bit. You should always consider how in your context that would be important. Change example from below to: user - username PASS - password of the user organization - owner of the project (you can find it in bitbucket url to your project) project - your project name "de
Read more

How to simulate slow connection (developer proxy in Node.js)

By K -
Image
Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy. Toggle device mode   Choose Network type. Refresh the page https://developer.chrome.com/devtools/docs/device-mode  Proxy: For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me. I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one. https://github.com/nodejitsu/node-http-proxy With this module I can write really short code to create slow server: var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host:
Read more