Halt and shave the yaks: How to add continuous delivery right now
summary
Argument: stop and fix the continuous delivery yaks now because small investments pay off. Concrete steps: put everything in Version Control, add a pre-merge build check in GitHub, run CI to catch failures earlier, and use canary deployments on Kubernetes to reduce blast radius. Measure with Dora metrics; humblebug drops change failure from ~50% to ~10% by adding a coverage gate and focused tests, and cuts test time from hours to ten minutes with sharded fast tests, enabling safer, more frequent deploys.
AI-written summary · about
chapters (7)
- 0:00Continuous delivery intro
- 3:15Defining CD terms
- 7:07Codebase releasable state
- 15:36Yak shaving importance
- 26:50Bringing pain forward
- 34:15Summary and next steps
- 35:17Q&A
related talks
40mAvoiding release paralysis
55mContinuously Delivering Continuous Delivery
46mHow to architect for continuous delivery?
46mSix small steps towards continuous delivery
41mContinuous delivery in 10 easy mistakes
24m"Misadventures in Continuous Delivery"
40mContinuous Delivery Anti-Patterns
35mTaming a beast