DevOps is Not War: No One Dies When Prod Goes Down
summary
Argues that clearer communication beats militaristic incident metaphors and shows concrete wins: US Strategic Command issues a call for DevOps and Agile modernization, Red Hat OpenShift is Red Hat’s Kubernetes distribution, and monitoring should shift to monitor AWS API calls to cut cloud bills. Cites Graham Allison’s Thucydides Trap where 12 of 16 rising-ruler pairs led to war, uses the UK/US 1916 economic shift as a peaceful handoff example, and shows network automation and CI/CD security hooks as practical, working steps.
AI-written summary · about
chapters (13)
- 0:00Welcome and introduction
- 1:02DevOpsish newsletter and background
- 2:46Military service and war parallels
- 4:31Thucydides trap and rising powers
- 9:23DevOps conflicts and fear
- 13:53US-UK power transition case study
- 17:04DevOps as cultural shift
- 19:53Automating infrastructure
- 21:18Security in DevOps pipelines
- 22:24Business processes and allies
- 24:10Change and failing fast
- 26:16Overcoming DevOps resistance
- 27:19Closing thoughts and quote
related talks
29mDevOps is Not War
22mDevOps is not a War
30mSurviving DevOps
17mDevOps Is Not Dead. Not Not by a Long Shot
39mDevOps is Dead? By the Way, What Is DevOps? And Why Should We Secure It?
41mDevOps for Java Developers (or maybe against them?!)
16mDevOps - Philosophy vs Practice
01h 02mWe have DevOps. No one was fired. But what to do?!