Go Faster, Be Safer
summary
Claim: shipping frequency increases without more testing by adding layers of mitigation using LaunchDarkly feature flags. Demo shows a kill switch that rolls back faulty releases in seconds and targets can be set precisely (example: roll out to 30% of London Android users). Integration example: Datadog auto-disables a flag when 500-errors spike, enabling automated rollback. Case study: eBay’s UI change instead of one big switch becomes daily tiny steps over 6–9 months to avoid customer outrage.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:34Why do we test changes?
- 6:08Testing is a good thing
- 7:08Safety is shipping frequently, with greater control
- 8:10Demo
- 9:37Fast - Safe
- 11:16Demo
- 12:07Fast - Safe
- 12:44Demo
- 14:45Integrations
- 15:52Many small changes vs. few big changes
- 19:44Visibility & control
- 20:38Impact on culture
- 22:01Summary
- 23:40TLDR;
- 24:31Outro
related talks
18mKeynote: Safe at any Speed - How Progressive Delivery Eliminates Risk
07mScaling with LaunchDarkly: A feature toggle story!
59mFaster & less risky releases with feature flags
07mKeep Calm and Deploy On: Creating Safer Releases with Feature Flags
02mA Message From LaunchDarkly
30mChoose Your Own Deployment: Interactive Feature Flag Adventure
14mReducing Release Risk with Feature Flag Management
56mEnabling continuous deployment with stealth, security, & smooth moves in mind