3 ms·
I haven't heard of module flag-driven development-- would love to hear more details. We manage the cleanup issue by defining a "removal branch" that cleans up
by jkodumal 11y ago
I haven't heard of module flag-driven development-- would love to hear more details.
We manage the cleanup issue by defining a "removal branch" that cleans up the feature flag at the same time the feature flag is introduced. This sticks around as a dormant pull request during the lifetime of the flag. It's not much overhead when this is done early. Cleanup does become painful when the code's not fresh in your mind.
Note that we do feature branches as well as feature flags-- trunk vs. branch based development is orthogonal to using feature flags.
- codazzo 11y agoClever!
- nobullet 11y ago'removal branch' is a great approach. Module Flag DD is how I call our approach :). There is no widespread notion for that .
- swsieber 11y agoI would love to see an expanded article on this - it would be great. This article is basically "Feature flags are great, and we can manage them for you". I'd love to see an article of "Here's a practical guide to using feature flags without hurting your codebase"