Feature Flags: A Boon or a Brake for a Team
summary
Examines when feature flags become harmful by creating dead code, higher cyclomatic complexity, and bloated regression tests, and presents concrete alternatives: INVEST slicing and the Hamburger technique to avoid partial releases; trunk-based development and Branch by Abstraction to eliminate branching flags; Strategy and Decorator patterns plus Domain-Driven Design to turn technical flags into explicit business rules; and Circuit Breaker for resilient handling of third-party services. Aims to stop using feature flags by default and keep them only where their trade-offs deliver real value.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:27Feature flags power
- 4:58Feature flag dangers
- 8:28Feature flags definition
- 10:11Three main use cases
- 13:21Alternatives to classic flags
- 14:03Trunk Based Development with flags
- 17:39Partial releases with flags
- 19:44User story splitting techniques
- 26:46Context-based activation rules
- 28:08DDD and business events
- 31:19Legacy migration patterns
- 34:09External dependency patterns
- 37:04Feature flag drawbacks
- 38:51Best practices for flags
- 40:18Q&A
related talks
26mMove Fast and (Don't) Break Things
05m5 Life Hacks Using Feature Management
51mFeature Flip to Achieve Flow
27mFlag Management Techniques That Support Development of Massive Apps
50mThe Story of One Feature Flag
08m⚡ Lightning Talk: The Hidden Costs of Feature Flags: Understanding and Managing Adoption Challenges
47mDr Sheldon Cooper Presents: Fun with Flags
15mFeature Flags