What the Military Taught Me about DevOps
summary
Deploys military practices like whiteboard Kanban to visualize pipelines and celebrate boards going green, shifts documentation from printed manuals to SharePoint wikis called "what's the fix," and replaces hand-editing 250 device configs by adopting tools like rancid backups. Builds a wheeled training rack as an ad hoc test environment because budget forbids lab gear. Cites hard failures that force change — a near‑detonation at Goldsboro, stolen top‑secret machines, and expiring crypto keys that brick devices — and shows incremental fixes and cross‑training that actually work.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:14Life before Devops
- 10:52Technical Orders
- 15:16Version-Control
- 16:34Physical Security
- 17:47Disaster Recovery Plans
- 20:38Failing Fast
- 26:48Military Failures
- 29:21How You Respond to Failure Matters Training Matters
- 30:16Intangibles
- 32:59The Good Idea Fairy
- 34:39Conclusion
related talks
05mDevOps over time
49mDevOps Ten Years After: Review of a Failure with John Allspaw and Paul Hammond
43mDevOps – when doing the right thing hurts!
29mDevOps Anecdotes
50mDevOps Project Failures - Lessons Learned and Strategies for Recovery
53mDevops notes from the field
53mGround Truths of a Rugged DevOps Practitioner
34mYou only have to change one thing to do the DevOps