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 September 2026 — rankings refresh with each new pull of comment data.

Books ranked

1,730

Published mentions

sum of exact per-book subreddit rows

392k

Members

Years tracked

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.

Guides built from this community

Ranked best-of lists and editorial guides that draw on r/ExperiencedDevs's tracked mentions.

By year

2026 2025 2024 2023 2022 2021 2020 2019

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. The Upvotes toggle re-sorts by comment-score weight — display only, the canonical order stays mention-count.

Sort by upvotes = sum of comment scores on recognized mentions

Designing Data-Intensive Applications

Martin Kleppmann

Martin Kleppmann walks backend engineers through every database, queue, and consistency tradeoff they'll eventually get paged about.

220 in this sub positive

Clean Code

Robert C. Martin

Robert Martin's case that unreadable functions are a discipline failure, not an inevitability, argued one renamed variable and one extracted method at a time.

180 in this sub critical

The Pragmatic Programmer

Andy Hunt

Two working programmers write down the shop habits senior engineers use so junior ones stop reinventing them badly.

92 in this sub positive

The Mythical Man-Month

Frederick P. Brooks Jr.

Fred Brooks managed IBM's late-1960s OS/360 project, then wrote the book explaining why adding more programmers only made it later.

89 in this sub positive

A Philosophy of Software Design

John Ousterhout

A Stanford professor who invented Tcl spends two hundred pages arguing that hiding complexity behind well-designed modules beats writing more, smaller methods.

86 in this sub positive

Staff Engineer

Will Larson

A senior engineer hits the ceiling of writing code alone and has to learn how influence works without a manager's title attached to it.

84 in this sub positive

Design Patterns

Erich Gamma

Four authors catalog twenty-three recurring object-oriented problems in 1994 and hand every future code review the same argument to have.

76 in this sub positive

The Manager's Path

Camille Fournier

A software engineer becomes a tech lead, then a manager, then a director, and the book insists on teaching you each rung separately.

76 in this sub positive

The Phoenix Project

Gene Kim

A struggling IT VP inherits a doomed project, a company on the edge of collapse, and one coworker who has quietly become the company's entire bottleneck.

76 in this sub positive

#10

Accelerate

Nicole Forsgren

Four researchers measure what actually makes software teams fast, and the findings keep getting cited against companies mistaking speed for shortcuts.

63 in this sub positive

#11

Working Effectively with Legacy Code

Michael C. Feathers

A consultant walks into a five-year-old codebase with zero tests and a deadline, and writes the manual for surviving exactly that.

60 in this sub positive

#12

Cracking the Coding Interview

Gayle Laakmann McDowell

The book credited with inventing the modern coding interview, argued about like it's also on trial for it.

54 in this sub Not scored

#13

Code Complete

Steve McConnell

Steve McConnell's seven-hundred-page argument that construction, not design or testing, is where most software quality is actually won or lost.

52 in this sub positive

#14

System Design Interview

Alex Xu

You get handed a whiteboard and forty-five minutes to design something like TinyURL, and this is the crash course for surviving that conversation.

51 in this sub positive

#15

Refactoring

Martin Fowler

Martin Fowler's method for restructuring code's internals without anyone outside noticing that anything changed at all.

48 in this sub positive

#16

Domain-Driven Design

Eric Evans

An interviewer asks if you've read Domain-Driven Design, then pivots to recursive Fibonacci when the answer gets complicated.

38 in this sub mixed

#17

Clean Architecture

Robert C. Martin

Robert Martin's rule: business logic sits at the center of the system, frameworks and databases plug in at the edges, never the other way around.

33 in this sub positive

#18

The Staff Engineer's Path

Tanya Reilly

An engineer keeps taking on the unglamorous coordination nobody assigned her and has to decide whether that work counts as leadership.

29 in this sub positive

#19

Peopleware

Tom DeMarco

DeMarco and Lister time how long it takes a programmer to get back into the zone after one interruption, then build a whole management argument around that number.

27 in this sub positive

#20

An Elegant Puzzle

Will Larson

Will Larson treats engineering management as a systems problem, headcount and career ladders, and r/ExperiencedDevs keeps filing it next to Designing Data-Intensive Applications.

21 in this sub positive

#21

The Unicorn Project

Gene Kim

A senior engineer gets exiled to a doomed payroll project and finds a rogue skunkworks team racing to save the company's flagship app before the deadline kills it.

21 in this sub positive