DEV Community

Discussion on: Using Feature Flags to troll our competitor without a line of code 😃

Collapse
 
kylessg profile image
Kyle Johnson • Edited

Do you think the use of feature flags is too invasive and may affect the normal operation of the program?

No I really don't, if used in the right way I see it as the opposite:

  • Coming from a place where I developed med tech and we had massive quarterly releases, the anxiety and likelihood of several massive changes causing issues were more of a threat to operations of a program and downtime vs consistently releasing with the safeguard of feature flags.
  • The idea that you can silently push new features (which I do all the time, daily.) testable by the internal team in production without affecting other users I'd say, is the opposite of invasive.
    • Being able to turn off a feature or configure it to avoid bugs and downtime is really quick. I see being able to react quickly more important than occasional incorrect flag/config changes.

What do you think about Launchdarkly's Code reference feature? Would a code analysis tool to help solve unexpected failures caused by Feature flag be useful?

Code reference checks are a good idea, but I don't think it really solves what you're talking about. What would solve that better is plugging in feature flag audit logs to monitoring like Datadog. For large scale apps that can catch issues, or on the positive side, improved conversion.