Just Enough Feature Flagging
summary
Feature flags let deployed code sit idle behind a conditional so QA can test in production with real data, marketing can demo to a subset, and finance can toggle a new calculation without a deploy. Use simple environment variable gates or vendor services like Split and LaunchDarkly to roll traffic gradually, provide a kill switch, and keep flags short lived — teams hit 300+ persistent flags and combinatorial testing pain when they forget to delete old conditionals.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:45What is feature flagging
- 7:00Common pitfalls without feature flags
- 10:08How feature flags work
- 13:17Use cases for feature flags
- 17:49Pitfalls of overusing feature flags
- 21:03Feature flags vs licensing
- 23:31Best practices for implementation
- 25:16Debugging and cleanup
related talks
41mFeature Flags: Separate Deployment from Feature Release
05m5 Life Hacks Using Feature Management
59mFaster & less risky releases with feature flags
05mFeature Flags
16mAdvanced Feature Flagging: It's All About The Data
44mFlags of Flexibility - Unlocking Rapid Iteration
30mChoose Your Own Deployment: Interactive Feature Flag Adventure
26mBuild Progressive Delivery and Safety Into Your Apps with Feature Flags