Twelve Essential Practices to be Effective in Continuous Delivery
summary
Claims twelve specific habits for reliable CI/CD and argues CI is a prerequisite and CD the goal, lists concrete steps: write automated unit/acceptance tests, use fakes for integration, put all artifacts in Git, commit and merge frequently so undo cost is zero, and automate database migrations (Liquibase or Rails migrations) plus infrastructure as code. Recommends immutable releases with blue-green and canary deployments, continuous monitoring, and says teams can push to production multiple times per day once these practices work.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:43The Problem with Waterfall
- 2:38Agile vs Waterfall
- 5:40Moses and Joshua
- 7:40Release the software
- 10:15Why not
- 13:00Dry Principle
- 17:00Fast Time to Release
- 23:40Two Types of Feedback
- 26:32Business Agility
- 28:37Discipline
- 31:18Good Quality Code
- 38:55Cognitive Dissonance
- 41:29Create Good Quality Code
- 42:53The Best Profession in the World
- 46:27Grow Up
- 48:10Use Fakes
- 49:32Version Control
- 51:25Merge Hell
- 52:53Cost of Undo
- 57:25Commit Frequently
related talks
01h 15mThe Practices That Make Continuous Integration
51mBetter software, faster: principles of Continuous Delivery and DevOps
24mCI/CD Best Practices to Deliver Software Faster
24mWhy, What, and How of Continuous Delivery
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
32mPractical Tips & Tricks for CI/CD Success
24mContinuous Delivery Best Practices
11mCreate unfair competitive advantage w/CI/CD Pipelines