5 ms·
Definitely feature flags. Forking the codebase will lead to much regret further down the line as the two forks continue to diverge and you spend most of your t
by simonw 6y ago
Definitely feature flags.
Forking the codebase will lead to much regret further down the line as the two forks continue to diverge and you spend most of your time trying to update them simultaneously or building features twice.
Feature flags mean you can keep all of your functionality on your main branch with the least amount of additional work.
This is a great guide to them: https://martinfowler.com/articles/feature-toggles.html https://martinfowler.com/articles/feature-toggles.html
- simonw 6y agoThe other technique that may be worth investing in is plugins. These could work if the following are true: - Many customers get their own independently deployed build of the software - Many future customers will want (and pay for) custom features that don't make sense for everyone else With plugins you can keep your core codebase from being slowly messed up by all of those custom one-off features, which is enormously valuable. My current principle project Datasette is the first time I've implemented plugin hooks and it's been working out really well for me: https://datasette.readthedocs.io/en/stable/plugins.html https://datasette.readthedocs.io/en/stable/plugins.html