[eshch]

it's very easy to realize how it can damage or ruin a project. it reveals once you need to implement a big feature to address some new business needs that can be critical for the company to survive. you have large code base and you should not break something. the clock is ticking, the rivals don't sleep, the market doesn't wait.

or you can just waste all the time firefighting with consequences of bad software.

it's not the only factor, but it can matter. the majority of companies i worked suffer from this. what really mitigates the problem is that competitors have the same problem on average.