3 ms·
> What should be done in a company that's basically committed every error you could commit? What's an engineer to do? Just switch jobs? Sometimes that's all yo
by flukus 10y ago
> What should be done in a company that's basically committed every error you could commit? What's an engineer to do? Just switch jobs?
Sometimes that's all you have the power to do. Why are customers leaving en masse if the old product is still functioning?
It sounds like the rewrite got stuck in the pattern where it has to do 100% of the original and then some. Just like a new product, a rewrite has to hit that MVP mark, just not as urgently. They also have to be able to throw out the cruft and not import every bad idea from v1.
- MichaelGG 10y agoMaybe competitors are providing a better product, so customers leave? It's hard to make a new version of a product that does less. Features were presumably mostly added for a reason, and customers probably use them. Removing them is a hard sell.
- flukus 10y agoIf there are better alternatives then sticking with the current technical debt may be a non-option as well. >Features were presumably mostly added for a reason, and customers probably use them. Removing them is a hard sell. Trying to make everyone happy is one of the big drivers of technical debt, a lot of stuff that gets added just to get that one critical contract. Sometimes you can refactor to better handle these variations that weren't anticipated, but sometimes you can't and you have to evaluate the complications versus that one customers business. You say this most often in businesses that practice sales team driven development.