Subreddit

Top books from r/programming

A general-purpose programming subreddit for news, articles, and discussion across all languages and disciplines, drawing a broad audience of working developers.

Updated September 2026 — rankings refresh with each new pull of comment data.

Books ranked

1,103

Published mentions

sum of exact per-book subreddit rows

6.9M

Members

Years tracked

About this ranking

r/programming's taste skews toward canonical craft books: Clean Code leads with 140 mentions and The Mythical Man-Month follows at 121, both outpacing anything the sub's closest neighbour r/ExperiencedDevs recommends in those slots. Where ExperiencedDevs fixates on Designing Data-Intensive Applications (247 mentions there, only 21 here), r/programming still puts C fundamentals near the top — The C Programming Language sits at 94 mentions, a count r/compsci barely matches at 26. Design Patterns (68) and Code Complete (56) round out a list that reads like a syllabus for writing better software rather than passing interviews or shipping ML models.

Guides built from this community

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

By year

2026 2025 2024 2023 2022 2021 2020 2019

Most-mentioned in r/programming

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

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.

253 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.

125 in this sub positive

The C Programming Language

Brian W. Kernighan

Two authors write the book that becomes 'K&R,' and forty years later Reddit still uses it as shorthand for programmers who had to know everything themselves.

94 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 critical

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.

57 in this sub positive

Structure and Interpretation of Computer Programs

Harold Abelson

Six chapters into Scheme, you're writing an interpreter for a language you invented an hour ago.

49 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.

46 in this sub positive

The Pragmatic Programmer

Andy Hunt

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

42 in this sub positive

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.

34 in this sub positive

#10

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.

28 in this sub critical

#11

The Art of Computer Programming

Donald E. Knuth

Four volumes of algorithms and combinatorics Donald Knuth started in 1962 and still hasn't finished, cited more often than it's actually read.

27 in this sub positive

#12

Designing Data-Intensive Applications

Martin Kleppmann

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

22 in this sub Not scored

#13

Refactoring

Martin Fowler

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

20 in this sub Not scored

#14

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.

20 in this sub positive

#15

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.

18 in this sub mixed

#16

Introduction to Algorithms

Thomas H. Cormen

A course syllabus gets posted, and a Redditor recognizes it as nothing but this book's chapter headings in disguise.

18 in this sub positive

#17

Code: The Hidden Language of Computer Hardware and Software

Charles Petzold

Charles Petzold builds a working computer from a doorbell, a flashlight, and a length of wire, then keeps going until it's running software.

16 in this sub positive

#18

Modern Software Engineering

David Farley

Dave Farley argues the real gap between a 10x engineer and everyone else is how much rework they eliminate before it ever happens.

15 in this sub Not scored

#19

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.

14 in this sub mixed

#20

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.

13 in this sub Not scored

#21

The C++ Programming Language

Bjarne Stroustrup

Bjarne Stroustrup writes the reference manual for the language he invented, and on Reddit it mostly survives as one joke about languages nobody complains about.

13 in this sub positive

#22

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.

13 in this sub positive

#23

Accelerate

Nicole Forsgren

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

12 in this sub Not scored

#24

The Design of Everyday Things

Don Norman

A cognitive scientist argues that when you can't open a door or use a stove, the door and stove are broken — not you.

10 in this sub positive

Looking for more? Similar subreddits

Subs whose top-mentioned books overlap most with this one.

r/ExperiencedDevs 47 r/cscareerquestions 46 r/learnprogramming 44 r/AskProgramming 29 r/devops 33