Feature Flag-Driven Development

The problem with FFDD is the code, full of "if"s. Some branches stay dead for months and years. When a feature is released, the flags need to be deleted and this becomes a challenging and boring task. Teams usually postpone these removals, setting the lowest priority. In my opinion, Module Flag-Driven Development gives much better results. Management agrees which set of features is released in a group as a module. Instead of "if" or "ifdef" engineers have a configuration of enabled modules. There is no need to delete a flag.

One question/concern I have always had -- Do you have multiple feature flags in place at once? How do you avoid the combinatoric increase in possible configurations? If you have feature A and B, what happens if A is turned on first? If B is turned on first? What if they are both turned on at the same time?

I like how one of the oldest concepts in programming, the ifdef, has now become (if you read the press) a "revolutionary idea" created by Facebook and apparently the core of a company's business. I'm only being a little sarcastic.

I would try it if you had a free tier for testing in dev.