4 ms·

> On top of that, once you finally get a feature merged and deployed, it can often happen that there’s a bug causing users to have a poor experience. Since your

> On top of that, once you finally get a feature merged and deployed, it can often happen that there’s a bug causing users to have a poor experience. Since your new feature lives directly in the code, deactivating it requires rolling back the code you merged, building it, waiting for the tests to run, and redeploying the application Why aren’t you using feature flags to gate new behavior/functionality?

ashenke 2y ago
This is literally what the article advocates. It pushes things to the extreme where every code you write would be on the main branch and behind a feature flag
- jtreminio 2y ago
  Feature flags have nothing to do with trunk or git-flow or feature branches. Simply, taking the entire introduction and asking, why are you not using common tooling?
  - jdlshore 2y ago
    It’s an advertisement for a feature flagging tool. I think you may have missed that.