Feature Toggles, Trunk-Based Development and Continuous Delivery

on YouTube ↗35m

" summary

Argues that switching to every commit to main plus automated CI/CD and thorough tests cuts cycle time from weeks to days by eliminating long-lived branches and reducing work-in-progress; demonstrates using feature toggles for percent rollouts and staged exposure to hide unfinished work, run experiments, and roll back quickly; shows backend flag storage and test-injected toggle states, warns about toggle debt and duplicate code, and reports teams that adopt this pipeline see faster feedback, fewer merge conflicts, and higher deployment frequency.

AI-written summary · about

" chapters (13)

1. 0:00Introduction and background
2. 3:06Complexity and software growth
3. 6:26Continuous delivery benefits
4. 10:50Automation and feedback loops
5. 13:11Problems with branching
6. 17:39Collaboration delays from branching
7. 20:55Trunk-based development explained
8. 22:35Handling unfinished features
9. 24:28Feature toggles and control
10. 26:48Testing with feature toggles
11. 28:58Feature toggle implementation levels
12. 31:10Managing large changes with toggles
13. 32:56Conclusion and key takeaways

" related talks

• 44mFeature Toggles: The Good, The Bad, and The UglyAndy Davies · NDC Sydney 2018
• 32mMaster your software delivery with feature flagsYoussef El Haddady · BlaBlaConf 2022
• 27mFeature TogglesDenis Brumann · phpDay 2017
• 33mCulture of Continue DeliveryLeena S N, Vaidy Bala · RailsConf 2014
• 27mTinkertoys, microservices, and feature management...Heidi Waterhouse · DevOpsDays Boston 2018
• 05m5 Life Hacks Using Feature ManagementSara Mazer · DevOpsDays London 2022
• 06mDeploying rapidly for continuous integrationHeidi Waterhouse · O'Reilly Velocity Conference 2017 - New York, New York
• 41mFeature Flags: A Boon or a Brake for a TeamDorra Bartaguiz · Devoxx France 2026