Every Scar a Story
summary
Argues that development method, version control, and deployment practice always change together and gives concrete prescriptions: move from long-lived branches and staging replicas to trunk-based development with feature flags, push small changes to production behind flags, and run progressive rollouts so you test real contracts with real data. Cites Git replacing lockout checkouts, staging replicas being prohibitively expensive, and performance goal of ~200 times a day deploys to reduce risk.
AI-written summary · about
chapters (9)
- 0:00Introduction and scars
- 1:29Organizational trauma and scars
- 8:01Staging servers as scars
- 9:24Code history and development methods
- 15:46Waterfall to agile transition
- 19:18Microservices and feature flags
- 25:28Speed equals safety in deployments
- 28:00Overcoming resistance to change
- 30:55Summary and Q&A
related talks
33mSoftware development practices for companies that want to make an impact
35mFeature Toggles, Trunk-Based Development and Continuous Delivery
05mGit as a continuous manager
35mQuickly and Safely Refactoring Legacy Code
38mBuilding a high quality product
01h 06mWaltzing with Branches
30m10 Ways to Improve How You Ship Software
01h 01mI deploy on Fridays (and maybe you should too)