I Deploy On Fridays
summary
Argues teams can safely deploy multiple times per day, even on Fridays by building fast, automated pipelines and better practices. Recommends a 10–15 minute pipeline, continuous testing layers, monitoring and exploratory testing, trunk‑based development, pair programming and feature toggles to decouple deployment from release. Uses patterns for confidence: canary, blue‑green and rolling updates plus strangler/expand‑contract for legacy migrations. Cites industry stats: far faster recovery (≈96×) and much lower change‑failure rates (≈5×).
AI-written summary · about
chapters (37)
- 0:00Intro
- 1:31DEPLOYING?
- 1:57BUT WHY?
- 2:18RISK
- 3:34CONTROL
- 4:11CONFIDENCE
- 4:54TRUST
- 5:31TIME TO REPAIR
- 6:01TIME TO RECOVER
- 6:13ON-CALL STRESS
- 6:36OVERTIME
- 7:10DON'T DEPLOY ON A FRIDAY
- 7:32I LIKE MY WEEKENDS
- 7:47WHAT ABOUT BUGS?
- 7:59WHAT ABOUT 3 PM?
- 8:25IMPROVE!
- 9:02FRIDAY IS 20% OF THE WEEK
- 9:18SMALL STEPS
- 10:46CONTINUOUS EVERYTHING
- 11:32CONTINUOUS INTEGRATION
- 12:18INTEGRATE AT LEAST DAILY
- 12:47CONTINUOUS DELIVERY
- 13:38CONTINUOUS DEPLOYMENT
- 16:44TRUNK BASED DEVELOPMENT
- 17:16ONLY COMMIT TO MASTER
- 17:48SHORT LIVED FEATURE BRANCHES?
- 19:22NO BRANCHES
- 21:16This pull request affects 31 files. could be a lot of conflicts if we don't merge it soon
- 23:35CODE REVIEWS
- 24:10CONTINUOUS INLINE CODE REVIEW
- 26:41FEATURE TOGGLES
- 30:04DEALING WITH LEGACY
- 31:00STRANGLER PATTERN
- 32:03BRANCH BY ABSTRACTION
- 33:18CONTINUOUS TESTING
- 35:12GOOD ENOUGH
- 35:38PIPELINE SPEED = KEY
related talks
47mI Deploy on Fridays (And Maybe You Should Too)
01h 01mI deploy on Fridays (and maybe you should too)
38mFearless Deploys on Friday Evening. Wait; what?!
46mContinuous Deployment Workflows
43mDeploying to Production on Friday
32mHow Your Deployment Strategy Influences How People Code
54mA FAIRY TALE FROM THE LAND OF HANS CHRISTIAN ANDERSEN
44mRelease Early, Often, Stable