"Failure" as Success: The Mindset, the Methods, and the Landmines
summary
Compares DevOps operations to the National Airspace: FAA logs 138,000 operations per day, procedures live in a binder of Terps approach plates that encode obstacle clearance, radios and approach procedures so pilots never see the ground. Recommends translating that into process primitives (unit tests, deployment requirements), encoded/automatable clearances, single-person ownership, value‑stream mapping, and explicit remediation. Cites Air France 447, automation surprise and drift into failure as failures to avoid and warns against blind automation.
AI-written summary · about
chapters (15)
- 0:00DevOps and culture intro
- 2:29DevOps craft to science
- 4:14Learning from aviation ops
- 6:05Visual vs instrument flight rules
- 8:16Why instrument-rated ops matter
- 10:48Standardization and primitives
- 13:58Precise communication power
- 17:38Expectations and responsibilities
- 19:04Remediation and dynamic systems
- 21:56Blind automation dangers
- 24:23Getting instrument-rated in DevOps
- 25:46Systems thinking and local ops
- 26:27Drifting into failure
- 28:56Current limitations
- 30:45Key takeaways
related talks
41m‘Failure’ as Success: The Mindset, the Methods, and the Landmines
17mDevOps Leadership in practice. True stories
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations
01h 06mCongratulations, you Failed!
35mMore Buzzwords Won't Help: The Long History of DevOps Failures
13mTen Ways to Doom Your DevSecOps
30mPilot your Project: Avoiding Anti-Patterns While Handling Incidents and Planning
25mThe Pursuit of Failure