Refusing to &quot;mess with something that already works&quot; is a recipe for disaster.<p>What companies often learn too late is that there are basically two options:<p>1. Make maintenance -- both in terms of upgrading underlying software, and addressing accumulated technical debt -- a regular, required part of their process, or<p>2. Occasionally face a potential existential threat from the unbounded cost of staying fixed in perpetuity to a stack that &quot;already worked&quot; once upon a time but no longer does due to lack of upstream support and available developers to keep it limping along.<p>The genuine problem is that &quot;what does this do for next quarter&#x27;s results&quot; is the only concern, which means long-term thinking is actively discouraged.