r/devops · 2024
Most-mentioned books in r/devops during 2024
This page ranks books by exact tracked mentions in r/devops within the published source unit for 2024. Counts come from the reconciled subreddit-by-month matrix; a source unit may be a bounded sample.
#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 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.
#3 The DevOps Handbook
Gene Kim
Four practitioners codify how Etsy, Netflix, and Google actually ship software — then explain why your org does the opposite.
#4 The Unicorn Project
Gene Kim
The Phoenix Project retold from the developer's chair: same burning company, different seat at the fire.
#5 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.
#6 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.
#7 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.
#8 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.
#9 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.
#10 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.
#11 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.
#12 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.
#13 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.
#14 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.
#15 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.
#16 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.
#17 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.
#18 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.