Faster & less risky releases with feature flags
summary
Feature flags let teams push code live turned off and then control exposure to users, enabling them to separate deployment from rollout and throttle by segments; common tactics include opt‑in early access, canary launches, private betas and dark releases. Rollouts use gradual percentages (start at 1% and ramp up) to test scalability and get real feedback, avoid long‑lived branches, bundle or entitle features per subscription, and remove flags when done — misconfiguring flags once cuts revenue by ~94% in a cited incident.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:11Edith Harbaugh
- 6:18Tsunami Software Releases
- 11:27Feature Flags!
- 12:14No long lived branches
- 19:42Early Access Betas
- 21:24Opt-In
- 22:13Block
- 23:35Rollouts
- 27:07Hypothesis Driven Development
- 30:52Subscription
- 35:54Best Practices for Feature Flagging
related talks
32mMaster your software delivery with feature flags
44mFlagging features — a DevOps approach to continuous release
41mFeature Flags: Separate Deployment from Feature Release
44mFlags of Flexibility - Unlocking Rapid Iteration
05m5 Life Hacks Using Feature Management
42mDeploy often, stress less: feature flags in production
14mReducing Release Risk with Feature Flag Management
56mWhen Feature flags go bad