Feature Flip to Achieve Flow
summary
The talk examines practical problems with feature flipping (feature flags) in software projects—combinatorial explosion of flag combinations, messy if/else code and neglected obsolete flags—and proposes alternatives and mitigations. It covers different prioritization strategies, dependency-injection–style designs, and smarter slicing approaches to make feature flagging easier to maintain and to present use cases, benefits and limits for non-technical attendees.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:27Subject origin
- 5:01Current flip problems
- 9:59Real use cases
- 13:52Flip alternatives
- 17:04Trunk based development
- 18:47Partial delivery
- 22:17Context-based activation
- 26:16Parallel versions
- 29:57External dependencies
- 32:02Explicit client demand
- 32:45Quick-fix solutions
- 37:06Team autonomy
- 38:09Non-prod environments
- 40:17Solution costs
- 43:30When flipping helps
- 44:53Flipping with trunk based
- 45:58A/B testing vs flipping
- 48:29Manual vs automatic flipping
- 50:18Conclusion & Q&A
related talks
41mFeature Flags: A Boon or a Brake for a Team
05m5 Life Hacks Using Feature Management
50mThe Story of One Feature Flag
28mLazy Brilliance
11m⚡Lightning Talk: No More If-Else Soup: Scalable Feature Flag Architecture With Design Patterns
50mFunctional Feature Flags
08m⚡ Lightning Talk: The Hidden Costs of Feature Flags: Understanding and Managing Adoption Challenges
26mMove Fast and (Don't) Break Things