Subreddit
Top books from r/AskProgramming
A Q&A subreddit where programmers of all levels post specific technical questions and ask for book recommendations to solve concrete problems.
Updated August 2026 — rankings refresh with each new pull of comment data.
About this ranking
r/AskProgramming skews toward fundamentals and craft over career strategy. Clean Code leads at 26 mentions, and The C Programming Language sits at 20 — a language-level classic that barely registers in r/cscareerquestions or r/learnprogramming. Code: The Hidden Language (18 mentions) shows up here at roughly half the rate of r/compsci (42) but outpaces every career-focused sub. Designing Data-Intensive Applications gets only 6 mentions, compared to 247 in r/ExperiencedDevs — this sub isn't thinking about distributed systems at scale, it's thinking about writing better code today. Working Effectively with Legacy Code at 14 mentions is a quiet signal: the people asking here are dealing with real codebases, not greenfield projects.
By year
Most-mentioned in r/AskProgramming
Ordered by tracked mention count across all published years. Sentiment is shown as context and does not change the order.
#1 Clean Code
Robert C. Martin
The book 536 Reddit threads cite when arguing about naming variables — revered by beginners, argued over by seniors.
#2 Code: The Hidden Language of Computer Hardware and Software
Charles Petzold
A retired software engineer builds a computer from telegraph relays and flashlights, one chapter at a time, until you understand what a CPU actually does.
#3 The C Programming Language
Brian W. Kernighan
The 1978 book that defined C's syntax, co-written by its creator, still cited by name 281 times across Reddit in 7 years.
#4 Structure and Interpretation of Computer Programs
Harold Abelson
MIT's 1985 Scheme textbook that 319 Reddit commenters have recommended and a noticeably smaller number have finished.
#5 The Pragmatic Programmer
Andy Hunt
Two veterans hand you a checklist for the craft: don't write code you don't need, own your tools, and fix the broken window before someone else does.
#6 Working Effectively with Legacy Code
Michael C. Feathers
Michael Feathers wrote the book for the developer who just inherited 30 devs' worth of code across 5 years in 5 different styles and has to ship next quarter.
#7 The Art of Computer Programming
Donald E. Knuth
Donald Knuth's multi-volume monument to algorithms: the book programmers cite in library lists and almost nobody finishes.
#8 Design Patterns
Erich Gamma
The 1994 Gang of Four catalog that named 23 object-oriented patterns, gave developers a shared vocabulary, and taught a generation to over-apply both.
#9 The Mythical Man-Month
Frederick P. Brooks Jr.
Fred Brooks spent the 1960s building IBM's OS/360 and wrote down everything that went wrong — in 1975, and it still lands.
#10 Code Complete
Steve McConnell
Steve McConnell's 900-page construction manual for software, ranked third on Reddit's canonical reading list and still cited 25 years after publication.
#11 Designing Data-Intensive Applications
Martin Kleppmann
A backend engineer's field guide to the tradeoffs behind every database, queue, and distributed system you will ever touch.
#12 Introduction to Algorithms
Thomas H. Cormen
The textbook four MIT professors wrote to settle every algorithms argument, cited by 254 Reddit commenters across 12 subreddits and still going.
#13 Refactoring
Martin Fowler
Martin Fowler's catalog of named moves for cleaning up code that already works, cited 116 times across Reddit in 7 years as the Clean Code alternative people actually prefer.
#14 Clean Architecture
Robert C. Martin
Uncle Bob's case for building software that survives its own success, bundled with opinions that provoke more argument than the architecture does.
#15 Effective Java
Joshua Bloch
Joshua Bloch's item-by-item case for writing Java the way the platform was designed to be used, with 90 independent recommendations that aged better than most of the language.
#16 The Clean Coder
Robert C. Martin
Uncle Bob's professionalism manual: say no to bad estimates, refuse death marches, and work the 40 hours then study on your own time.
#17 A Philosophy of Software Design
John Ousterhout
A Stanford professor's 200-page rebuttal to Clean Code, built on interface depth rather than method length.
#18 C++ Primer
Stanley B. Lippman
The 1,000-page C++ textbook that r/learnprogramming recommends by name whenever someone asks how to learn the language seriously.
#19 Domain-Driven Design
Eric Evans
Eric Evans's 2003 blueprint for modeling software around business domains — cited in interviews, assigned in grad programs, rarely finished.
#20 Head First Design Patterns
Eric Freeman
A pattern book that shows up on every 'essential reading' list while experienced devs debate whether you still need the Head First version.
#21 Modern Software Engineering
David Farley
Dave Farley argues that software engineering is a discipline with repeatable principles — 73 Reddit threads mostly shrug, then mostly agree.
#22 Release It!
Michael T. Nygard
The book that named the circuit breaker pattern, written for engineers who've watched their own services fail at 2 a.m.
#23 Software Engineering at Google
Titus Winters
Google engineers document how a 25,000-person org ships software that has to last decades — the distinction between 'programmer' and 'engineer' is the whole argument.
#24 The C++ Programming Language
Bjarne Stroustrup
Bjarne Stroustrup's own manual for the language he built — 1,300 pages that explain every design decision, including the ones you're cursing right now.
Looking for more? Similar subreddits
Subs whose top-mentioned books overlap most with this one.