Fearless Deploys on Friday Evening. Wait; what?!
summary
Claims a team can safely deploy on a Friday evening by combining concrete practices: TDD with a goal of 100% test coverage, tight continuous refactoring (turning 3-hour rewrites into 10–15 minute tweaks), fast feedback via pair programming and rotating pairs, and CI/CD with feature toggles, monitoring and automatic rollbacks. Evidence includes a team that deployed 24 times a day and the prediction of only one or two real bugs per year when these practices are in place.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:10Alexs background
- 3:01A short story
- 4:13Software Development
- 7:03Bugs
- 12:48Test Suite
- 16:29Acceptance Driven Development
- 19:52Acceptance Criteria
- 22:47Refactoring
- 24:55Refactoring and bugs
- 26:43Continuous refactoring
- 29:11Continuous integration
- 31:34Pair programming
- 33:58Importance of social skills
- 34:56Peritation
- 36:21Live on Master
- 37:09Conclusion
related talks
01h 01mI deploy on Fridays (and maybe you should too)
44mI Deploy On Fridays
47mI Deploy on Fridays (And Maybe You Should Too)
43mDeploying to Production on Friday
32mHow Your Deployment Strategy Influences How People Code
54mA FAIRY TALE FROM THE LAND OF HANS CHRISTIAN ANDERSEN
33m7 habits of a high performing team
31mFireside Chat: Continuous Deployment