I deploy on Fridays (and maybe you should too)
summary
Argues that safe Friday deploys are achievable by shrinking risk with automation and practices: a Jenkins pipeline, automated unit/integration/end‑to‑end tests, monitoring, feature toggles to decouple deploy from release, and trunk‑based development with pairing or mobbing. Cites research: high performers deploy ~50x more and recover ~100x faster with a 5x lower change‑failure rate. Shows a search rewrite behind a flag ramped 10→50→100% with better metrics and a pipeline time cut from ~25 to ~12 minutes so deployments work.
AI-written summary · about
chapters (34)
- 0:00Intro
- 1:56DEPLOYING?
- 3:32TRADITION
- 5:54CONTROL
- 7:26CONFIDENCE & TRUST
- 11:35WHAT ABOUT THURSDAY?
- 13:38BIG STEPS
- 13:50SMALL STEPS
- 14:13REDUCE RISK
- 17:19PROJECT
- 17:59CONTINUOUS INTEGRATION
- 19:42CONTINUOUS DELIVERY
- 21:00CODE IS ALWAYS IN A RELEASABLE STATE
- 21:45CONTINUOUS DEPLOYMENT
- 24:12AUTOMATION AUTOMATION AUTOMATION
- 25:06DEALING WITH "LEGACY"
- 25:30STRANGLER PATTERN
- 31:42DELAYING INTEGRATION
- 32:33BRANCHING STRATEGIES
- 34:03TRUNK BASED DEVELOPMENT
- 36:00PULL REQUESTS?
- 36:14CODE REVIEWS ARE USEFUL
- 36:35BUT: FLOW DELAY
- 38:44PAIR PROGRAMMING
- 39:38CONTINUOUS INLINE CODE REVIEW
- 42:35MERGING FEATURES?
- 43:19FEATURE TOGGLES
- 46:16FEATURE TOGGLE DEBT
- 48:20PIPELINE AS CODE
- 49:01CONTINUOUS TESTING
- 53:06NO TEST SUITE DETECTS EVERY ISSUE
- 53:23PIPELINE SPEED = KEY
- 54:36CANARY
- 56:21ROLLING UPDATE
related talks
44mI Deploy On Fridays
47mI Deploy on Fridays (And Maybe You Should Too)
38mFearless Deploys on Friday Evening. Wait; what?!
43mDeploying to Production on Friday
46mContinuous Deployment Workflows
32mHow Your Deployment Strategy Influences How People Code
46m10+ Deploys Pe
33m7 habits of a high performing team