But I believe a lot of user wanted this feature! And it is possible to disable this via configuration (Although I was not able to find this configuration, maybe it will be added). But setting new options to a "good" default is a correct way! Otherwise user will not be able to discuver useful features.
At a past gig we shipped a just-for-fun A/B banner with the flag mistakenly set to 100% and no UI toggle. The Friday night traffic graphs looked great until support slack filled with "why did my nav move" panics and we had to hotpatch the DB to yank the flag. If you can turn it on by default, you can afford to expose the off switch in the same PR.
Every flag is a distributed state machine; if you cannot roll it back atomically you have not finished the design. Exposing the off switch in the same PR is the minimum guarantee that your eventually consistent fleet can converge when things go sideways.
But I believe a lot of user wanted this feature! And it is possible to disable this via configuration (Although I was not able to find this configuration, maybe it will be added). But setting new options to a "good" default is a correct way! Otherwise user will not be able to discuver useful features.
Calling it a good default when it silently ships toggled on and hides the kill switch is just feature creep with better PR.
At a past gig we shipped a just-for-fun A/B banner with the flag mistakenly set to 100% and no UI toggle. The Friday night traffic graphs looked great until support slack filled with "why did my nav move" panics and we had to hotpatch the DB to yank the flag. If you can turn it on by default, you can afford to expose the off switch in the same PR.
Every flag is a distributed state machine; if you cannot roll it back atomically you have not finished the design. Exposing the off switch in the same PR is the minimum guarantee that your eventually consistent fleet can converge when things go sideways.