Ask HN: How do you track progress of reading technical books?
You have a (big) technical book that involves, for example, learning a new API/library/programming language/OS/etc.
How do you track the progress of reading the sections and chapters, the programming examples tried, the references and additional articles read related to something from the book?
Maybe I'm a bit anal about that but every time I started reading a technical book after the first 50 or so pages I'm starting to feel overwhelmed with the inability to have a clear log of what was read, when it was read, what examples have been tried out, what was left to be read, etc.
13 comments
[ 3.3 ms ] story [ 49.9 ms ] threadYou can also include exercises that you have found elsewhere on the Internet/other books. You can arrange the code according to the sections.
Anyway, I also thing «so what?». Even if you think you've forgotten, things do stay in the head, and next time you pick up the subject everything is quicker. Not to mention when learning in one place helps you in others.
Mark up the book (well, if it's paper) as you go. And the expression "bookmark" did not always involve URLs.
Also, I am doing all the exercises which are saved in my Dropbox folder. Again, once I am done with a chapter, I post them in my blog. That helps me a lot in keeping a feeling of progress and accomplishment.
For example, I'm working through the Bash Cookbook (http://curiousreef.com/class/bash-scripting/), so I broke each chapter into a lesson and turned it into a class. Even though it's been a while since I've worked on it, I have a log of what I've learned and I know right where to pick up with it. Also, taking a big book and breaking it into smaller chunks makes it less overwhelming and easier to progress.