Subreddit
Top books from r/devops
A subreddit for practitioners and engineers working in DevOps, focused on culture, tooling, automation, and the organizational side of software delivery.
Updated August 2026 — rankings refresh with each new pull of comment data.
About this ranking
r/devops is dominated by two books to a degree unusual even among technical subs: The Phoenix Project pulls 324 mentions and The DevOps Handbook 174, together accounting for the vast majority of all recommendations. That pair has almost no presence in r/learnprogramming or r/programming, where the conversation centres on language fundamentals and craft. Continuous Delivery (42 mentions) and Accelerate (32) round out a list that stays tightly focused on deployment pipelines and organizational change rather than algorithms or language idioms. Designing Data-Intensive Applications shows up at 28 mentions — high enough to signal that infrastructure engineers here care about data systems, though nowhere near its dominance in r/ExperiencedDevs (247 mentions).
By year
Most-mentioned in r/devops
Ordered by tracked mention count across all published years. Sentiment is shown as context and does not change the order.
#1 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.
#2 The DevOps Handbook
Gene Kim
Four practitioners codify how Etsy, Netflix, and Google actually ship software — then explain why your org does the opposite.
#3 The Unicorn Project
Gene Kim
The Phoenix Project retold from the developer's chair: same burning company, different seat at the fire.
#4 Continuous Delivery
Jez Humble
The 2010 Humble-Farley textbook that turned "ship when it's done" into a measurable engineering discipline with pipelines, gates, and deployment rings.
#5 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.
#6 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.
#7 TCP/IP Illustrated, Vol. 1
W. Richard Stevens
W. Richard Stevens wrote 24 Reddit-cited pages per year's worth of networking protocol detail so you'd stop guessing what's on the wire.
#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 Systems Performance: Enterprise and the Cloud
Brendan Gregg
Brendan Gregg's 800-page field manual for diagnosing CPU, memory, disk, and network bottlenecks on Linux and cloud systems.
#10 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.
#11 An Elegant Puzzle
Will Larson
Will Larson's field guide to engineering management, written from actual operating experience at Digg, Uber, and Stripe.
#12 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.
#13 Effective Python
Brett Slatkin
Brett Slatkin's 90-item guide to writing Python the way the language actually wants to be written.
#14 Fluent Python
Luciano Ramalho
The Python book r/Python recommends when you're done with the tutorials and need to know what the language actually does.
#15 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.
#16 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.
#17 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.
#18 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.
#19 Computer Networking: A Top-Down Approach
James F. Kurose
Kurose and Ross walk the network stack from HTTP down to the wire, so the physical layer arrives after you already understand why it exists.
#20 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.
#21 Modern Operating Systems
Andrew S. Tanenbaum
Tanenbaum's textbook walks through every layer of an OS — scheduling, memory, file systems, threads — one chapter at a time, with the implementation details left in.
#22 Python Crash Course
Eric Matthes
The author built it for high school students who kept getting lost — 126 Reddit mentions later, it's still the default first Python recommendation.
#23 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.
#24 System Design Interview
Alex Xu
Alex Xu's interview prep guide that one r/cscareerquestions commenter credits with landing his current job.
Looking for more? Similar subreddits
Subs whose top-mentioned books overlap most with this one.