[cogman10]

Happens when you do the flags wrong :)

We have a FF as a service platform and a big "value add" is that we can turn on and off features at the client level with it.

But, unfortunately, it's both not the only mechanism for this and it is also being used for actual feature flags and not just client specific configuration.

I'm personally a MUCH bigger fan of putting feature flags in a configuration file that you deploy either with the application or though some mechanism like kubernetes configs. It's faster, easier to manage, and really easy to quickly answer the question "What's turned on, why, and for how long". Because, a core part of managing feature flags is deleting them and the old code path once you are confident things are "right".

The biggest headache of our FF-ws is that's really not clear and we OFTEN end up with years old feature flags that are on with the old code path still existing even though it's unexercised.