Why DevOps is like firefighting at sea
summary
A naval firefighting model maps to DevOps through concrete practices: a fire in the engine room is contained in ten minutes and cooling/repairs finish within two hours on a 180-person ship, because of three attack levels (scout, breathing-device teams, fully suited specialists), strict prevention (scheduled maintenance, no debris = reduce technical debt), frequent drills including simulated production outages and daily fire drills, short command lines and earned trust, the right tools (thermal camera, foam, Halon equivalents, monitoring) and deliberate train in production exercises.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:04Fire alarm on Navy frigate
- 3:35Technical center and fire response
- 5:20Three fire attack levels
- 7:50Debrief and aftermath
- 8:30DevOps like firefighting
- 9:12Fire prevention first
- 10:41Technical debt hazards
- 11:44Daily fire drills
- 13:32Chaos in production
- 14:56Controlled incident practice
- 15:38Multi-skilled teams
- 16:40Team maturity and incidents
- 17:21Trust in emergencies
- 18:46Leadership in incidents
- 19:49Short command chains
- 20:51Decentralized decisions
- 21:54Right tools and access
- 22:57Monitoring alarms
- 23:4024/7 readiness
- 24:44Investing in people
- 25:29Q&A
related talks
01h 02mWe have DevOps. No one was fired. But what to do?!
29mHunting the DevOps Whale
58mHow we killed DevOps by creating a dedicated DevOps team
58mDevOps @ Scale — Greek Tragedy in Three Acts
52mDevops @Scale
24mHow DevOps changed the way we operate software
51mElemental devops
36mWhat the Military Taught Me about DevOps