Feature Toggles: The Good, The Bad, and The Ugly
summary
Clear operational rules and hard numbers: a reused feature toggle plus a partial deploy causes Night Capital to lose 450 million dollars in 45 minutes when seven of eight servers run new logic; HP switches from eight-week branch feedback to two-day trunk-based testing by moving model flags to startup config; a staged email rollout uses RabbitMQ and a release toggle over six to eight weeks, then deletes the flag after four. Concrete C# examples, toggle types, and remediation patterns are shown — actionable war stories, not abstract advice.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:34PowerPeg and SMARS
- 5:40Dead Code
- 7:00Name Toggles Well
- 7:16STARTUP PERIODIC FLEXIBILITY
- 14:46Branch By Abstraction
- 29:45Complexity
- 32:23Testing is harder
related talks
43mFeature Toggles: The Good, The Bad and The Ugly
30mFeature toggles: ask us anything
36mIt's More Than Feature Toggles: ...
01h 09mFeature flags: the toggle, the A/B test and the canary
20mFeature Flag-Driven Development… in Reverse
18mTrunk Based Development and Feature Toggles
51mFeature Toggles, or How to Deploy Features Without a Release
30mChoose Your Own Deployment: Interactive Feature Flag Adventure