feature flagging allows you to separate code deployment from feature releases. It’s a change in dev methodology/mentally and usually goes hand-in-hand with “trunk-based development” (trunk/master is always stable and you should avoid long lived branches).
a good feature flag service should also allow you to do % rollout to try to de-risk the release of a new feature, some times even auto-closing the feature if some specific metric passes a certain threshold (e.g. dau dropped 10%, number of errors increased x%, etc)
a good feature flag service should also allow you to do % rollout to try to de-risk the release of a new feature, some times even auto-closing the feature if some specific metric passes a certain threshold (e.g. dau dropped 10%, number of errors increased x%, etc)