Ten years after reading it, people still say "we have a Brent problem." Brent is a character in a novel about servers that keep crashing: the person nothing ships without, whose knowledge never leaves his head. If your last production release happened on a Saturday night, you know who yours is.
Around that novel sits a small library on shipping software and on how to organize the teams doing it. I have read six of them and written a reading note for each. Here is the order I would follow, and what you can leave on the shelf.
The novel that makes it click
The Phoenix Project (Gene Kim, Kevin Behr and George Spafford, 2013, 8.2/10) does what whole shelves of manuals fail at: it teaches flow management to someone who has never opened a management book. You go through three outages with the hero before the mentor explains anything, and by the time he does, you needed it. Unplanned work becomes a task board emptied by emergencies. The bottleneck becomes Brent.
Let's be honest: as literature, it is an airport novel. Characters who are really functions, a cartoon villain, a mentor with an answer for everything. The setting (storage arrays, change approval boards) is 2013, and the transformation lands in four months, which is a fairy tale. In real life, count years. But the setting aged because the book won: deploying ten times a day, unthinkable then, is routine now. For modern recipes, my note points to The DevOps Handbook, which I have not covered here.
The numbers that win the argument
Accelerate (Nicole Forsgren, Jez Humble and Gene Kim, 2018, 7.4/10) put numbers into a debate that only had slogans. Before it, "we should deploy more often" was a conference opinion. After it, it is the outcome of four years of research, replicated since. Burying the approval committee became my favorite meeting argument: I am not the one saying it, the study is.
The limit: it argues a case, it is not a manual. You learn what to aim for, not how to get there. The reading is sometimes dry, repetitive near the end, and the ×46 and ×440 figures date from 2017. Keep the frame, not the values: capabilities over maturity, outcomes over activity. For current numbers, my note sends you to the free annual DORA reports.
The how, at last
Continuous Delivery (Jez Humble and David Farley, 2010, 463 pages, 7.8/10) is the foundation of half my job. I never ran CruiseControl and I won't pretend otherwise. What the book gave me is the why behind the buttons I press: why one binary travels, why the same script everywhere, why you deploy without releasing. With those reasons, you stop tinkering and start designing.
All the tooling has aged. Hudson, Ant, first-generation Puppet: mentally swap in GitHub Actions, Docker, Kubernetes, Flyway. Containers did not exist yet, Docker arrived in 2013. The book is thick and sometimes dry, and the authors themselves suggest dipping in rather than swallowing it whole. Do that. The principles have not aged a day: a modern CI pipeline is the deployment pipeline of chapter 5.
The shape of teams
Team Topologies (Matthew Skelton and Manuel Pais, 2019, 8.2/10) is a rare management book: written for developers. Its real gift is vocabulary. Once you can say "that's a distributed monolith" or "we need an enabling team here," a vague friction becomes a nameable problem, and so a fixable one. The inverse Conway maneuver (design the teams to get the architecture you want, since architecture ends up copying the organization) is worth the read by itself.
It is repetitive, its case studies are thin, and it is about organization design: you often need management's blessing to apply anything. Don't expect a recipe to run solo on Monday morning. Read it as the companion to Accelerate (the data) and The Phoenix Project (the story).
The human side, and the old-timers
Peopleware (Tom DeMarco and Timothy Lister, 1999 edition, 8.2/10) showed, with data, that projects fail for human reasons. I am a developer, not a manager, so I won't play the expert. But the chapter on flow put words on something I have felt for years: that fifteen-minute climb back into a problem, and the rage of being yanked out of it, which almost no workplace protects. The 1987 world shows through (open offices, landline phones, zero remote work), and a few anecdotes land oddly. Read it less for the offices than for the mirror.
The Mythical Man-Month by Frederick Brooks (1995 edition, 7.8/10) was written in 1975 about a disaster from 1964. Brooks ran OS/360 and, instead of downplaying it, he dissected it. Every law comes from something that really broke. The technical parts date (program clerks, static overlays), the mechanisms do not: adding developers to a late project makes it later. Skip the 1975 vocabulary, keep the laws.
The order I would follow
Book
Pages
Rating
What it is for
1
432
8.2
Understanding flow through a story
2
288
7.4
Convincing with data
3
463
7.8
The why of the pipeline, dip in
4
240
8.2
Naming and drawing teams
5
245
8.2
Protecting flow, reading people
6
322
7.8
Answering "let's add two people"
Conclusion
The oldest of these six books, written in 1975, is also the one whose main law no revolution has cancelled: not Git, not agile, not the cloud. And the newest one on teams admits that its framework is not enough without culture and engineering practices. Delivery tools change every five years. Problems between people never do.
I stitched the marrow of dozens of tech books into a single thread, from bits and Big O up to the AI era: that is The Developer's Great Book. Continuous Delivery, The Phoenix Project, Accelerate and Peopleware are folded into the level "Prove it, ship it, hold the load." Team Topologies, Peopleware and The Mythical Man-Month come back at the level "Software is for humans."
📚 Other comparisons. Best Clean Code and Refactoring Books, and the Order to Read Them and Best Event Sourcing and CQRS Books, and the Order to Read Them.
Top comments (0)