I've worked on shitty code with shitty tests that ran the core of the business. Even while doing that, it was horrible to work with, held important features bac

I've worked on shitty code with shitty tests that ran the core of the business. Even while doing that, it was horrible to work with, held important features back and drove talented people away, leaving everything to stagnate in a "this works enough" state. When the wind changed, it was hard to turn the ship around, important people got nervous, and things got into a bad spiral. None of this is the failure of code and tests alone; but both can be indicative of the structural health and resilience of the wider situation.