Explain like I'm five · SW Eng

What is DevOps?

DevOps, told as a story about tearing down the wall between the writer and the printer, and trading small batches often instead.

done! all finished!this can't be printed as it is?throw a manuscript over the wall, and problems only surface at the print shop

The writer throws the manuscript over the wall.Throw a manuscript over the wall, and problems only surface at the print shop.

once it's written, my part's doneI just print whatever I'm handedeach watching only their own part — problems surface only at the very end

When responsibility is split, problems get caught too late.Each watching only their own part — problems surface only at the very end.

DevOps = tearing down the wall and printing together, in small frequent runswriter and printer stand side by side, with no wall, trading small batches of pages often

DevOps tears down the wall between writer and printer so they print together in small, frequent runs.Writer and printer stand side by side, with no wall, trading small batches of pages often.

Tear down the wallthe writer and printer, once separate, work as one team
Ship small, ship oftensmall frequent runs instead of one big one
Automate the linechecking and printing run automatically
Share the responsibilitywhen something breaks, writer and printer fix it together
THE OLD WAYonce a quarter, one big batchthe printer finds problems only after receiving itbig batches take longer to fixTHE DEVOPS WAYevery day, small batcheschecked automatically before printingsmall batches get fixed fast

Split the batch smaller, and the problems get smaller too.The more often you ship, the less there is to fix each time — so fixes take less time too.

now we work togetherbut security doesn't take care of itselftearing down the wall doesn't solve security

Tearing down the wall doesn't solve security.Printing fast together doesn't automatically take care of security. Bringing a guard into that too is a different story → the builder and the guard, side by side.

In one breath

DevOps = tearing down the wall between the writer (dev) and the printer (ops), and printing together in small, frequent, automated batches.

DevOps is a culture and set of practices that get development (Dev) and operations (Ops) working as one team instead of separate silos, shipping small changes often through an automated pipeline of continuous integration (CI) and continuous delivery/deployment (CD). Success is measured with metrics like deployment frequency, change lead time, change failure rate, and recovery time.

When grown-ups say it

DevOps
The writer and the printer, with no wall between them. Development and operations work as one team.
Continuous Integration
Merging manuscript changes often, in small pieces. Every merge gets checked automatically.
Continuous Delivery/Deployment
Automatically feeding a checked manuscript onto the print line. Continuous delivery keeps a human approval before release; continuous deployment ships automatically.
Zero-Downtime Deployment
Swapping in a new edition without closing the bookstore. Specific methods include blue-green and canary → running twin rides, one at a time, a quiet test run in the corner.
Infrastructure as Code
Writing down the print shop's own setup as text, too. The equipment itself can be version-controlled like a manuscript → the blueprint-as-code in the SRE field.
Shared Responsibility Culture
The attitude of writer and printer fixing problems together, not pointing fingers. Puts 'let's fix it together' ahead of 'whose fault is it'.
DORA Metrics
The rulers that measure whether DevOps is working. Deployment frequency, lead time, failure rate, and recovery time are the classics; DORA now adds rework rate as a fifth → the four classic metrics.
DevSecOps
Bringing a guard into the wall-free space too. The broader version that brings security in from the start, too → the builder and the guard, side by side.
Next story
The Reading Room Opened With a Single Form →
Want another term as a picture book? Request →