Why feature flags are BAD

Call me crazy, but I think features flags are mostly bad and often cause more issues than they solve to a few reasons:

1. It creates lazy thinking. A feature flag is often an easy way to not think deeply about the configuration and admin experience of a new feature. I've found myself over the years saying "just put it behind a feature flag" when I didn't really want to think through how a user may want to manage the feature themselves.
2. It creates a really messy codebase. This is especially true when features start interacting with each other and one feature flag behavior impacts another feature flag.
3. Because of point #2, it puts a ton of pressure on the product, support and customer success team to learn about each feature flag and understand how they work. I can't even count the number of times I messed up a customer's environment because I turned a feature flag on or off without understanding all the ramifications.

Are feature flags all bad? No! They can be useful when launching a completely experimental feature that might die on arrival. But if that feature gets picked up, the feature flag should be removed as quickly as possible.

#productmanagement #productmanager

Видео Why feature flags are BAD канала Fabi.ai: Your AI data analyst for all your data