r/devops · 2023
Most-mentioned books in r/devops during 2023
This page ranks books by exact tracked mentions in r/devops within the published source unit for 2023. 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 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 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.
#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 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.
#7 An Elegant Puzzle
Will Larson
Will Larson's field guide to engineering management, written from actual operating experience at Digg, Uber, and Stripe.
#8 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.
#9 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.
#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 Effective Python
Brett Slatkin
Brett Slatkin's 90-item guide to writing Python the way the language actually wants to be written.
#12 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.
#13 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.
#14 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.
#15 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.
#16 The Linux Programming Interface
Michael Kerrisk
A 1,500-page tour of every Linux system call, written by the man who maintains the manual pages.
#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 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.
#19 The Staff Engineer's Path
Tanya Reilly
A staff engineer's actual job — navigating ambiguity, protecting your team from org chaos, and delivering on projects nobody owns — laid out by someone who did it.
#20 Thinking, Fast and Slow
Daniel Kahneman
A Nobel laureate maps the two systems running your brain — and shows how often the faster one gets you killed in a bull market.