Subreddit
Top books from r/ExperiencedDevs
A subreddit for software engineers with professional experience to discuss career growth, architecture, engineering culture, and the realities of working in large codebases.
Updated August 2026 — rankings refresh with each new pull of comment data.
About this ranking
Designing Data-Intensive Applications dominates with 247 mentions — more than double anything else on the list — which signals a sub preoccupied with systems that actually have to work at scale. Management and org dynamics get serious weight here: The Manager's Path (94) and Staff Engineer (73) have no meaningful presence in r/learnprogramming or r/programming, where those titles barely register. Cracking the Coding Interview pulls 76 mentions despite being interview prep, which tracks for a community debating whether the hiring process is broken. The contrast with r/cscareerquestions, where CTCI leads at 525, is telling: ExperiencedDevs treats it as one data point, not the whole curriculum.
By year
Most-mentioned in r/ExperiencedDevs
Ordered by tracked mention count across all published years. Sentiment is shown as context and does not change the order.
#1 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.
#2 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.
#3 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.
#4 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.
#5 The Manager's Path
Camille Fournier
A software engineer picks up a management role and finds out — via 142 Reddit mentions — that nobody told them about the crying, the firings, or the 90-day onboarding clock.
#6 Staff Engineer
Will Larson
Will Larson interviews the staff engineers Reddit wishes it had access to and explains what they actually do after they stop writing code all day.
#7 The Phoenix Project
Gene Kim
An IT manager inherits a failing project, a mutinous ops team, and a CEO deadline — and has to ship before the company does.
#8 Clean Code
Robert C. Martin
The book 536 Reddit threads cite when arguing about naming variables — revered by beginners, argued over by seniors.
#9 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.
#10 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.
#11 Cracking the Coding Interview
Gayle Laakmann McDowell
The book that turned software hiring into a sport — written by the ex-Googler who introduced programming challenges to the process in the first place.
#12 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.
#13 System Design Interview
Alex Xu
Alex Xu's interview prep guide that one r/cscareerquestions commenter credits with landing his current job.
#14 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.
#15 Accelerate
Nicole Forsgren
Nicole Forsgren's research team ran the numbers on software delivery and found that deployment frequency and stability move together, not against each other.
#16 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.
#17 An Elegant Puzzle
Will Larson
Will Larson's field guide to engineering management, written from actual operating experience at Digg, Uber, and Stripe.
#18 The Unicorn Project
Gene Kim
The Phoenix Project retold from the developer's chair: same burning company, different seat at the fire.
#19 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.
#20 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.
#21 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.
#22 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.
#23 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.
#24 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.
Looking for more? Similar subreddits
Subs whose top-mentioned books overlap most with this one.