Feature Flags
summary
Explains a concrete rollout workflow: add a flag in a config, wrap new behavior in an if statement (example name: Facebook audience revamp), ramp from 0–100% and monitor logs with kibana and gore fana, revert to 0% if errors spike. Uses a dog-borrowing app as a toy scenario and cites MailChimp metrics: 120 engineers seeing about 50 deployments a day after adopting flags. Emphasizes cleaning up flags to avoid technical debt.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:13Why use Feature Flags
- 3:53Deploy early
- 5:44Test in production
- 6:54How to add feature flags
- 8:20How to use feature flags
- 8:59Ramping up feature flags
- 12:17Technical debt
related talks
05mFeature Flags
59mFaster & less risky releases with feature flags
05m5 Life Hacks Using Feature Management
41mFeature Flags: A Boon or a Brake for a Team
32mMaster your software delivery with feature flags
27mFlag Management Techniques That Support Development of Massive Apps
50mThe Story of One Feature Flag
26mBuild Progressive Delivery and Safety Into Your Apps with Feature Flags
