4 ms·
Feature flags give you orthogonality. When you have an `if False:` or equivalent in code, you have to deploy to enable a new feature, so if the current state i
by perlgeek 3y ago
Feature flags give you orthogonality.
When you have an `if False:` or equivalent in code, you have to deploy to enable a new feature, so if the current state in the test environment isn't good, you either have to wait for it to be fixed, or to roll back all possibly bad new commits before you can enable the feature.
Another feature of feature flags is that a non-coder can toggle them.
If you need neither of these, sure, go ahead with commits and deployments instead.
- hinkley 3y agoWhen you're trying to triage a production problem or explain what happened between Saturday and today, orthogonality isn't a feature, it's a challenge to be overcome.
- JimDabell 3y ago> if the current state in the test environment isn't good, you either have to wait for it to be fixed, or to roll back all possibly bad new commits before you can enable the feature. This is a symptom of long release cycles. The more work you “save up” to deploy all at once, the more difficult deployments become. Everything becomes much easier when you minimise unreleased work.
- vichle 3y ago> Another feature of feature flags is that a non-coder can toggle them. This is not a feature, and it will get you called in during the weekend at some point.