3 ms·
> Just reading through all the old issues would require a larger team than the product revenue could sustain, Yeah, well, if it weren't so full of decades-old
by CRConrad 5y ago
> Just reading through all the old issues would require a larger team than the product revenue could sustain,
Yeah, well, if it weren't so full of decades-old still-unsolved bugs, then maybe the product would have more users and therefore more revenue?
- asoneth 5y agoThat's a good point in general, though the product example I gave was primarily funded by government contracts and (at least based on the negotiations) the contracts were far more sensitive to price than quality. But I will say that my experience in enterprise software has been similar. The relationship between software quality and company success is more a bell curve than a linear one: if you neglect quality you'll certainly lose customers, but above a certain point if you spend too much of your budget fixing every bug you'll eventually lose to competitors with mediocre quality but lower prices and/or more capabilities. It's all about finding the right balance.