How to Read Programming Books

- What if I’m unfamiliar with the programming language of the book?

Don’t be frightened if you have difficulty following the book due to an unfamiliar programming language. Instead, go to its documentation (or check out codecademy.com) and learn how to use variables, types, functions, and control flow. This knowledge will get you through most programming books.

Code examples in many books are mostly there to demonstrate ideas (unless the book is there to teach you the syntax and features of a programming language). Treat examples as pseudo-code, focus on the concepts, and ignore details that get in the way of learning.

- I find reading the programming book formidable.

Challenging oneself is good, but don’t forget that we read to learn. If you don’t understand what you are reading, you are likely not learning much. Having encountered problems related to what you are reading helps you understand the material and ideas.

If the difficulty of the programming book prohibits learning, then there is no shame in stopping to read and revisit the programming book another time.

I’ve read many books I found difficult. For example, the first time I tried to read Design Patterns by Gang of Four, I struggled and gave up as I didn’t learn much. After reading Head First Design Patterns, I later gave it another chance and appreciated the book much more.

I created this website as a resource to help others in their journey to becoming great software craftsmen by assisting them in reading books in an efficient order.

- Reading programming books is very time-consuming.

Read programming books at your own pace. Reading many (or demanding) programming books is not prestigious, but gaining knowledge and perspective is, so read programming books to improve yourself, not impress others.

Making a habit of reading is essential. Always keep the programming book you are reading close at hand and find opportunities to read. Reading on the commute to work can be very efficient, or start the day with 15 minutes of reading during breakfast. Do what works best for you, whatever it may be.

- What do I do once I have finished reading a programming book?

Reading alone will not make you a good programmer. Instead, one must practice or challenge the ideas the author is trying to teach.

You will likely forget the details if you don’t practice what you read. Always keep practicing and challenge yourself. I find it very rewarding to revisit programming books after I have tried to apply the ideas I’ve learned. Usually, I find something new to take away from the book.

I would also recommend starting a book circle as an alternative way to explore the content of the programming book.

- Is it worth doing the exercises in the programming book?

Many programming books contain exercises, and doing them will cement what you’ve read. So, should you always do them? It depends on your experience and skill. The less experienced you are, the more exercises you should do.

I don’t do most exercises in programming books anymore. If I can solve it in my head within minutes, I usually don’t bother to write the solution in a text editor.