Not Actually a DevOps Talk, or, Beyond “Survival is Not Mandatory”
summary
Argues that real change comes from improving the software process: adopt a small-batch loop (hypothesis → code → put in front of users → observe) and automate a platform so teams can deploy multiple times a day. Gives IRS example: call centers hang up ~63% of callers, so showing exact amount owed on a web page cuts calls and raises usage. Recommends rotating pair work, pick low‑risk pilots (Home Depot’s pro tool rental and paint desk), and scale deliberately for 19,000–30,000 developers.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 3:54Digital transformation reality
- 14:44Avoiding the tire fire
- 21:02Organizing for success
- 27:46Scaling the transformation
- 30:14Q&A and closing
related talks
30mSurviving DevOps
01h 02mThe Enterprise DevOps Challenge
01h 01m"Doing Devops" as a politically powerless developer
01h 02mWe have DevOps. No one was fired. But what to do?!
34mYou only have to change one thing to do the DevOps
40mBetter Living by Changing Less – IncrativeOps
29mDevOps Anecdotes
54mEffective DevOps for Organizations