
Coding Chats Should you ship code without feature flags?
Dec 18, 2025
Software engineer and feature ops advocate Melinda Fekete joins to discuss the pivotal role of feature flags in managing code releases. She highlights the challenges of upkeep and emphasizes centralizing flag definitions for efficiency. Melinda explains the significance of user feedback and dogfooding in refining products. They explore the benefits of testing in production, particularly in mitigating outages, and caution against the overhead of unnecessary flags in small projects. Key insights on deployment strategies and the importance of operational safety round out their engaging chat.
AI Snips
Chapters
Transcript
Episode notes
Manage Feature Flags As Lifecycle Items
- Treat feature flags as lifecycle artifacts with clear ownership and expiry dates.
- Tie each flag to a ticket and make flag cleanup part of the definition of done.
Centralize Flag Definitions And SDK Usage
- Keep one central source of truth for flag definitions and use an abstraction SDK for consistency.
- Use good naming, avoid recycling flags, and ensure one flag does one thing only.
Use Flags For Gradual Rollouts And Dogfooding
- Feature flags enable gradual rollouts by enabling code at runtime for small user segments.
- Dogfood internally first, then expand to percentages while monitoring metrics and feedback.
