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

You don’t need to read these books end to end.

The a builds on b builds on c style of learning is only one way of learning things, and in many cases, the foundations (a, b) serve you no real value.

Just jump to the sections that interest you (c) and go back to previous sections if you feel like you’ve lost track of what they’re talking about.

For example, the first 20 pages of ‘Remote’ cover why remote working is good. It is intended for people who are considering if remote working is suitable. If that’s not relevant to you, do not waste your time reading it.

Of course, you still have to actually sit and read the chapters that interest you… but, if you struggle with that for the chapters you’re actually interested in perhaps a more project based (do a thing, use references from book) approach, or notes based (treat book as study text, rewrite it as your own notes) might work for you.

…but, don’t feel bad. These are super boring ass books with a few interesting parts to them.




Books have been written on how to read a book.

Often, it’s some variant of starting with studying the table of contents then doing a fast first pass of the text. That’s usually a pretty good way of figuring out where to start.


> doing a fast first pass of the text

Does that mean reading it end to end?


Sometimes yes but not always. It depends on the book.




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

Search: