Fireside Chat: Continuous Deployment
summary
Defines continuous deployment as every commit to main goes to production without manual checks and argues that doing so simplifies the release workflow, cuts cost and lets teams ship experiments in minutes (author cites deployments visible in ~20 minutes and cases that survive Black Friday traffic). Book documents databases, testing-in-production, observability, pipelines, feature flags and release strategies, and includes seven published case studies from fifteen companies showing it works in high‑stakes retail. Key claim: deployments become routine technical events when tests and flags are in place.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:27Continuous deployment importance
- 2:33Favorite nerdy book
- 3:56Defining continuous deployment
- 5:01Book contents
- 9:05Why a book was needed
- 11:35Advantages over manual checks
- 14:48Barriers to adoption
- 18:05Continuous deployment with juniors
- 20:10Starting continuous deployment
- 23:02Release vs deployment
- 27:37Unifying goal for improvement
- 28:42Blog to published book
related talks
23mContinuous Deployment - The Last Frontier for Continuous Delivery
41mAll Things Continuous
51mBetter software, faster: principles of Continuous Delivery and DevOps
46mContinuous Deployment Workflows
55mThe Rationale for Continuous Delivery
32mHow Your Deployment Strategy Influences How People Code
22mPath to Continuous Deployment
24mWhy, What, and How of Continuous Delivery
