d'bug shares Web development advice, including CSS, JavaScript, PHP, Java, .NET and Ruby on Rails tips and tricks.

Would you read programming books if I offered you free pizza?

• Posted by Brian
• Posted on April 30th, 2008
• View Comments

Do you remember Book It!, the reading incentive program by Pizza Hut that is still available to elementary school teachers? Just like the Scholastic Book Club before it, both provide children with an exciting avenue that fosters reading. It meant gold stars, the admiration of your peers, and quiet nights under the covers accompanied only by a flashlight and the intoxicating smell of an old library book. Of course, it also meant free pizza.

In our industry there appears to be some backlash against the reading of programming books in particular. I wonder if a nostalgic incentive would blow the winds of change. Would the re-introduction of free pizza and gold stars encourage you to visit your local book store? How about if I sent you a rickety flashlight and a fluffy comforter emblazoned with G.I. Joe characters to read under?

Jeff Atwood recently wrote about the sad fact that most programmers do not read programming books in his post Programmers Don’t Read Books — But You Should. Like the majority of content on the Web today, it was gleaned by few and misinterpreted by many. Jeff, like myself, actually loves a good programming book. The best of these books are timeless, and have a considerably long shelf life. Even the best language-specific references can offer nuggets of wisdom that stand out among the unremarkable majority.

The excuses are plentiful. Programming books suck is the commonly accepted defense. Books are too expensive is another — information on the Web is free. Besides, programmers do not learn by reading, they learn by writing. One hand on the mouse, and the other flipping pages leaves no room for typing. Our field ebbs, flows and swings in too many directions, so books are dead before they are even published.

I can agree to some extent with those sentiments. Nevertheless, there is a glaring contradiction that eludes even the most staunch detractors who scoff at reading programming books. Scientifically speaking, reading benefits you. Oh sure, any type of reading benefits you, but given your choice of profession, reading good programming books will really benefit you. If you do not believe me, perform a search on the phrase “the benefits of reading”. Then, consider the following:

Reading programming books increases your ability to communicate technical concepts

In elementary school they call this comprehension and expression. You may not be surprised to find out that the majority of programmers are completely unable to teach other programmers. The reason is primarily due to a lack of comprehension and expression. Coding is accomplished principally through memory recall, with little forethought into the execution. That means when someone else asks you how to do the same thing, you may have a hard time explaining it to them.

Especially if you have a great long-term memory, you can recall several programming techniques, but it is a singular experience. From your brain to the tips of your fingers, and onto the computer monitor. It is a great annoyance listening to programmers who complain incessantly about the novice in the cubicle next to them, but after closer investigation nothing is being done to remedy the situation. Holding hands is not necessary, but a greater ability to communicate alternative methods of engineering solutions is absolutely mandatory.

This is only going to be possible if you can take those highly specialized and technical concepts in your head and form them into coherent sentences. The best way to accomplish this is by reading authors who are doing exactly that.

Reading programming books helps you to understand the why, and not just the how

This is a follow-up to the previous point, but it concentrates on the benefits to you personally, as opposed to the benefits to others. Not only will you be able to communicate technical concepts to your esteemed colleagues, but you will understand why you do what it is that you do. This is the insignia worn by master programmers. It is a badge of honor that is recognized by all because it demonstrates that above everything else, you have passion. You are ill-content with piecing together a solution that does nothing except meet a deadline.

That has peripheral benefits as well. Because you understand why, you can feel comfortable questioning the how. You can disagree with commonly held perceptions because you are well read on several viewpoints, and can speak to each fluently. Experience in the field helps here as well, since academic viewpoints are typically frowned upon unless they are accompanied by work history. Yet, even if your career has been short-lived, if you are well-read it demonstrates initiative and drive.

In the long run most programmers are unhappy with the status quo, but only those who know the why can make a significant impact through change.

Reading programming books introduces you to refined (edited) paradigms

I would not venture a guess as to the ratio, but well-edited programming books are diamonds in the ruff compared to the plethora of cubic zirconia dotting the landscape. Programmers are notoriously bad at grammar and spelling, which is why technical writers can make a good chunk of change for a living. Digging up these priceless gems (okay, enough with that analogy) is difficult, but when you find one, you want to read it, re-read it and re-re-read it again.

These books offer up refined paradigms, and before getting to you they have passed through the hands of other authors, a technical editor, an editorial staff, friends and even family. That is one benefit of reading a programming book. Although it seems implausible, it will be more accurate, or at least on par with anything you will read on the Internet. At this point some of you are reeling with objections, but this is the harsh reality. Even if these books are a flop due to the lack of depth and organization, what is written will undoubtedly be factual.

I have been guilty of tossing out some poorly contrived notions and code samples myself because no one else was reading over my shoulder. No blogger is perfect. No author is perfect either. The latter, however, will always be at an advantage.

Reading programming books distinguishes you from your peers

The final benefit of reading programming books is intrinsic to the activity itself. It will distinguish you from your peers. It is doubtless a hardy majority will take my advice and go on a reading binge, but if you are one of the few who do, then you will be set apart from your coworkers. Even if the classics do not grace your personal library, do yourself a favor and read something remotely related to programming and software engineering. Pick up a book on startups, some tycoon’s biography, business management, usability and information architecture, or design.

Get a better handle on the industry you work in, and you will soon find that others use you as a reliable source of information. A wealth of knowledge is available to you. Please do not wait for your free Personal Pan Pizza reward coupon in order to acquire it.

Tags: books, programmer, programming, read