Hacker News new | past | comments | ask | show | jobs | submit login

Indeed.

For me, I'd say reading the Summary is a good start to know if you want to read a book, but just because the basic idea is in that, I don't think it's all you need. I often find myself taking notes on different things than others have and linking it to other things in different ways.

You need to fully understand the Why and although there is an argument that most books are only a few ideas, the stories in the book help argue why these are important an help you see how those ideas fit into the world and how they fit, something that is truly important if you are going to start implementing that idea or thought into your way of thinking, else it's just another article you read on wikipedia that you nod your head too.

The human brain is all about patterns and connections and that is missed on a single article that is making a big point, a summary is exactly that, a good way to explain things in a simple and quick way, but you have to understand everything else behind it for you to truly understand it and for that you really need the whole book, unless you have a badly written book that fails to do this. I think this is vastly missed by those that just read summaries or dismiss the power of the whole book, just reading something doesn't really ingrain it into you, you have to wrestle and think about it in your own mind and being exposed to that idea from all different directions for a few hours really helps cement it.

It's also why I am considering rereading books I liked, even though I still remember the basic ideas and due to what I mentioned earlier, I think you can take different things from the same book if you read it at different points in your life, different connections will happen and different points will make more sense than they did before.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: