Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Jeff Atwood’s 2008 essay, “Programmers Don’t Read Books – But You Should,” is a case for treating books and online answers as complements—not competitors. Search and Q&A sites can deliver a quick fix; a well-chosen book can help explain principles that remain useful after a language, IDE, or platform changes. The essay’s claim that programmers rarely read books is historical rhetoric, not a current measurement of the profession.
Do programmers read books?
Atwood’s title is deliberately provocative, not the result of a survey showing that programmers as a whole do not read. In the essay, published on 28 April 2008, he quotes Joel Spolsky saying, “Programmers seem to have stopped reading books. The market for books on programming topics is miniscule compared to the number of working programmers.” That is Spolsky’s assertion as quoted by Atwood; the essay does not provide a sample or method to establish it as a measured rate.
Atwood also reproduces a passage attributed to DeMarco and Lister’s Peopleware: “The statistics about reading are particularly discouraging: The average software developer, for example, doesn’t own a single book on the subject of his or her work, and hasn’t ever read one.” The essay does not document the underlying study or its methods, so this should not be read as a description of developers today. No contemporary reading-rate statistic is established here.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Read Atwood’s point, then, as an argument about what books can offer—not proof that programmers have abandoned them. The essay and its quotations are available in Atwood’s original article.
#1 Best Overall
Are programming books still useful when online answers are faster?
They can be, because speed and depth answer different needs. Atwood acknowledges the convenience of finding programming information online. A targeted search or a question-and-answer site may be the quickest way to resolve a particular error or learn how to use a specific feature. That convenience does not necessarily provide the broader explanation behind a design choice, a practice, or a recurring problem.
Atwood’s case for books is strongest when the material explains ideas that outlast a particular tool. He describes the best programming books as those that “transcend choice of language, IDE, or platform” and explain “why,” not only “how.” The distinction is practical: instructions tied to a changing interface can go stale, while a sound discussion of software design, usability, or teamwork may remain applicable across projects.
Books are not automatically valuable because they are books. A long text that is irrelevant to your work or never gets finished has little practical advantage over a concise online explanation. Atwood’s advice is to choose practical books you will read and, more importantly, put into action. Use online sources for immediate, specific questions; turn to a book when you want a sustained treatment of an idea and can apply it.
Which books did Atwood recommend?
Atwood named five books for working programmers. His essay presents them as practical, reusable reading, not as a ranked list or a buying guide. It does not compare editions, prices, formats, or present-day availability.
| Book | What Atwood’s recommendation supports | What to check before choosing it |
|---|---|---|
| Code Complete 2 | One of the practical books Atwood recommends to working programmers. | Confirm the edition and whether its material fits the programming practices you want to study; the essay does not assess current edition status. |
| Don’t Make Me Think | One of Atwood’s five recommendations. | Consider whether usability is relevant to your work. The essay does not compare editions or assess current availability. |
| Peopleware | One of the recommended books; Atwood also quotes a passage from it about developers’ reading habits. | Choose it if its subject matter fits your needs. The essay does not verify the quoted passage’s underlying statistics. |
| The Pragmatic Programmer | One of Atwood’s five practical recommendations. | Check that the edition you find suits your needs; Atwood’s essay does not specify an edition or compare versions. |
| Facts and Fallacies | One of the books Atwood includes in his recommended set. | Verify the exact title, edition, and availability before buying; the essay provides no buying details. |
Use the list as a starting point, not a guarantee that every title is right for every reader. Match a book to a question you actually face, check that the edition is appropriate, and favor a book whose ideas you are likely to use. Atwood also suggests that rereading can yield deeper insight; that is an argument for returning to useful material, not a claim that one reading method suits everyone.
How should you decide whether to read a book?
- Name the problem or skill. Be specific: are you looking for a quick fix, a reference for a tool, or a durable understanding of a practice?
- Choose the format for the job. For a narrow, immediate question, an online answer may be more efficient. For a connected argument or a broader foundation, consider a book.
- Check relevance before committing. Look at the book’s subject, edition, and scope. Atwood’s 2008 list does not establish present-day edition status or availability.
- Plan to apply what you read. Connect the ideas to a real project, code review, design decision, or team practice; otherwise, finishing the book may not change your work.
Where does Stack Overflow fit?
Atwood explicitly presents Stack Overflow as complementary to classic programming books. That framing resolves the apparent either-or choice: a community Q&A site can help with a specific problem, while a book can provide a more sustained account of concepts and practices. Neither format makes the other unnecessary; choose according to the question you need to answer.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
