Tales from the DevOps Transformation Trenches
summary
Consultancy engagements show that tools alone don't fix culture: teams rename old roles and still hit slow release gates like a release board that meets twice a year or an 84-step pre-approval that turns a ten-minute cloud provision into three months. Microservices without consumer-driven contract tests become distributed monoliths that break everything; reuse with stubbed components causes catastrophic failures (Ariane, Mars Orbiter). Recommendations: automate tests, practice CI/CD with trunk-based commits daily, use feature flags and deferred wiring, surface build status and remove blocking processes.
AI-written summary · about
chapters (15)
- 0:00Start
- 6:01every time we change code, something breaks
- 6:28distributed monolith
- 7:14mars climate explorer
- 10:58microservices need automated integration tests
- 17:28what's stopping more frequent deploys?
- 20:23vertical slices
- 20:35back-first development
- 20:48feature flags
- 24:51this provisioning software is broken
- 26:36does the process add value?
- 27:05this is the test team... who don't have the skills to automate their tests.
- 27:37our tests aren't automated
- 27:54it costs too much to releas
- 31:02transformation endurance
related talks
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
29m5 ways to screw up your DevOps Transformation
30mA Story of DevOps Transformations
38mDevOps transformation – the good, the bad and the ugly
21mBuilding A DevOps Culture in a Remote World
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations
41mContinuous delivery in 10 easy mistakes
45mMarried to DevOps