4 ms·
Ideally you would avoid this situation, but if you find yourself here: a good mitigation strategy is feature flags. If it's been agreed to build feature Y for o
by usea 10y ago
Ideally you would avoid this situation, but if you find yourself here: a good mitigation strategy is feature flags. If it's been agreed to build feature Y for one customer, then enable that feature for only that one customer. It's not a panacea, and won't necessarily help with your tech debt, but it will help the product stay focused from a user perspective.
FWIW, every product I've worked on has gone through this.
- alex_hitchins 10y agoI worked on a large codebase with this approach of 'feature for x'. It will not scale, IMHO. Far better to agree with someone wanting feature N is that if you want it and it's a good fit for the majority of users, you pay for it - everyone gets it. It is a hard problem to tackle, especially given the sums involved in delivering sometimes trivial-effort features.