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

There's a trick when reading nonfiction: read the table of contents, then flip ahead and read the entire index. You now have a good understanding of what topics the book covers, and where in the book they are. You can crank through a stack of 10 or 20 books and get a good sense of which ones are really worth reading. 'Half of all knowledge is simply knowing where to find the knowledge.'



Also read the last page of every chapter, and you can avoid 90% of the fluff if it's non-fiction.

Authors start with a short draft that is only juice and then add spam to make it into a book. That initial juice is the summaries of chapters that you find on the last page or two. The initial part of the chapter is just fluff and examples to drill the point down because they think you need 10 examples for each concept in order to justify paying as much for a blog post as you would for a book.


Thank you for commenting this. I can imagine this being supremely useful, especially if you decide to go ahead and read a book and it tells you much more than you would've guessed :) (either the titles/index are bad, or the content is good)


Some authors even put fanservice in the index.




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

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

Search: