3 ms·
I work at a company that uses feature flags heavily for releases. Even most refactors are done behind a flag. It works surprisingly well, especially when you h
by jovanni 10y ago
I work at a company that uses feature flags heavily for releases. Even most refactors are done behind a flag.
It works surprisingly well, especially when you have 20 developers all trying to release different features at the same time, you then have a controlled way to isolate enabling and monitoring each new feature one at a time.
It's generally expected that you clean up your flag conditions after things have been tested. And that you write code so removing the flag flow is trivial.
- avita1 10y ago> Even most refactors are done behind a flag How does this work without cloning vast swaths of code and saying: if (feature) loadModuleA(); else: loadModuleB();
- jovanni 10y agoOn occasion you do that. But usually it's just a couple if statements in a couple places with very little code duplicated. Also, again, it's expected that after it's tested you delete the old path. It's a short lived transitional situation. Sometimes it's annoying. Overall it's safer when you're on a massive scale.
- flukus 10y agoThat would tie in cleanly with an IOC container.
- deleted 10y ago[deleted]