Skip to main content

Book Review: Mastery by Robert Greene

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 On the other hand, I have found also critic of the slate article: 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 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


Popular posts from this blog

Course Review: The Bitfountain iOS 8 with Swift Immersive

This is second big iOS learning project. For first one read iOS Programming book review. As I only have two of them done I have to compare them somehow.

I am mindful that it took me a really long time to finish it (since last autumn). For a couple of months this year I didn't even have the internet to learn it, so it could not be helped. But last half of the June I've spent watching the videos every day and managed to finish it before any new internet problems.

So how was it?
In my opinion, it's great if you're starting out. There are a lot of basics, and seeing how to do things in XCode just makes your learning much easier than looking at the photos in the book. On the other hand, learning is more shallow and it is much easier to just follow the videos and learn only the basics without bigger picture about iOS SDK. I somehow missed more challenging exercises (even though I don't like to do them ;)

Course it pretty long but many videos are quite short (1-2…

How to Learn when Life is Short

I haven't really think this through but I have read really interesting articles recently and I just wanted to write for myself later.

Life is Short by Paul Graham

It's just that, learn from people older that you what is most important, and that life actually is short...

Instead of Goals or Resolutions, Try Creating Rules by Leo Babuta

In the time of New Year Resolutions, it's good to read something that is proposing different way of achieving things. Still I see much more value in habits than setting goals. But...

The Easy Way To Learn Hard Stuff by Per Harald Borgen
It's something that I read from time to time and I know it works sometimes for me. The things I learn then are really learned and something Jakub Wasilewski  has told me many times to do. Still it's uncomfortable and for some reason, I have failed to use this method more than once or twice. Writing it here so maybe I can think about it more and figure out how to do that more often.

Towards an understandin…

Hero's Journey in Presentations

Artur Skowroński recommended me: Want a Better Pitch? Watch This. by Andy Raskin and I think it is so great and applicable to all kinds of talks that I want to help it get more popular.
So the plan of presentation is going to follow these steps: Enemy - ProblemWhy now? - call to actionShow how the world will look like without the problemProblemsEvidence that you fixed the problem The image at the top is because it reminds me of Hero's Jurney. It has fewer steps but there is a lot of similarities. Especially #3 made me realize that grand vision of the future is something that I should have used in my talks.  The result at the start of the presentation makes a lot of sense actually. Everyone already knows that I speak about something because I probably fixed it and if you tell about it at the end then it might be hard for some people to see the bigger picture in the solution you're going to present.