The Cost of Speed: Rethinking "Move Fast" in DevOps
summary
Argues that unbridled “move fast” breeds hidden costs: mounting technical debt and burnout, expensive third‑party licenses, security gaps, and messy quick fixes that later break production. Recommends measurable practices: unit, integration and acceptance tests at every stage, automated pipelines and lightweight review tooling to keep changes small. Gives concrete examples: a five‑person team producing 13,000 pull requests in six months and a Volkswagen/Audi project that needed 18 months for proper infra and safety—making the case for sustainable speed (velocity with direction and guardrails).
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker intro
- 1:50Why speed became DevOps obsession
- 3:39Startup pressure driving speed culture
- 5:07Hidden costs of rushing development
- 7:19Quick fixes and their long-term damage
- 8:06Sustainable speed vs reckless speed
- 10:18Real-world example from Volkswagen Group
- 11:23Automation as sustainable speed tool
- 12:54Quality culture and patience in tech
- 14:26Pull requests and code review best practices
- 16:31Project management pitfalls and focus
- 17:57Building team trust and accountability
- 19:22Developers as company capital
- 20:53Creating stable team environments
- 21:13Balancing speed and production stability
- 21:57Q&A and closing remarks
related talks
29mEconomies of Speed
01h 00mDevOps – Value at Speed
45mThe astonishing value of speed
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
12mSAG Expert Interview #08: Fast Flow for agile & safe software deployment
42mSpeeding Up Innovation
51mThe astonishing value of speed
27mDevOps Reality Check: Feels Faster or Really Faster?