Catastrophes and Atrophies
summary
A company runs its service on a single box under desk then tries to swap the whole stack to Linux, Oracle and NetApp in a six‑ to eight‑week migration that stretches into days of emergency scripting and lost customers; another team uses per‑team CI so API changes require three months to integrate; a startup adopts continuous deployment successfully but spends three months building prepaid‑shipping integration while a competitor ships a 20‑minute hack; the claim: small, fast experiments beat big rewrites.
AI-written summary · about
chapters (10)
- 0:00Introduction and personal story
- 2:12First catastrophic migration
- 13:54Lessons from extreme programming
- 17:29Rewriting platforms without reason
- 22:43Continuous integration failure
- 25:53Success with continuous deployment
- 33:19Building the right product quickly
- 36:30Plato’s cave and adoption of change
- 38:16Embracing failure and risk
- 40:22Q&A and closing remarks
related talks
18mAchieving Innovation and Stability for Enterprises
05mAdventures In Enterprise: Lessons Learned Promoting DevOps In A Legacy Organization
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
41mModernizing Legacy Apps - Platforms and Strategies
55mDevOps @Scale (Greek Tragedy in 3 Acts)
46mEmbracing Collaborative Chaos
42mSpeeding Up Innovation
35mLiving in a Hybrid World