4 ms·
The reality of software development is that any project beyond a handful of devs requires branching. This branching can be achieved in at least two ultimately
by tsimionescu 3y ago
The reality of software development is that any project beyond a handful of devs requires branching.
This branching can be achieved in at least two ultimately equivalent ways:
- literal branches in your VCS of choice (or forks, clones, etc)
- literal runtime branches, via IF on feature flags
When a feature is ready to merge to prime time, the branches have to be merged, and unexpected interaction with other features can now be found. This is exactly as likely to happen when doing a git merge as when setting a feature flag to true.
Different features working in isolation but interacting badly is a fundamental aspect of software and not some incidental self-caused problem that can be prevented by a better development methodology.
To take a somewhat silly example - if one team is working on a feature to make error messages more readable and another team is working on a feature to make error messages opaque IDs looked up in a manual, these two features will obviously clash when they go live regardless of whether they were each behind a feature flag or on separate git branches. Hopefully few organizations would schedule such an obvious conflict of features, but more subtle versions happen all the time.