3 ms·

Here are a couple of ways in which feature flags can be better than branches: QA can try in-development features out together easily. Some flags can be used ope

Here are a couple of ways in which feature flags can be better than branches: QA can try in-development features out together easily. Some flags can be used operationally to turn off non-essential features during periods of high load (for a service, that is). There's no free lunch, but flags can be a useful tool. https://martinfowler.com/articles/feature-toggles.html https://martinfowler.com/articles/feature-toggles.html

joshribakoff 9y ago
The fun starts when you have a multi tenant system, and you end up with some users having the flags enabled and some not having them enabled. You may find that you have to support both "branches" in the long run. Which can be a good thing in the sense your product is more configurable, but also entails a lot of the same grievances of branching because you end up supporting multiple variations of a feature. Or multiple combinations thereof
- dangoor 9y ago
  Yeah, totally agree about the danger there. Flags should have a defined lifetime. I've been in that multi tenant hell, and concur that it sucks.
  - sroussey 9y ago
    Agreed. They need a defined lifetime and a defined migration (as needed, for either the feature or control).