But why should you care?
You've moved on with your trail of collateral damage by then, reaped the benefits and the fixer will subconsciously take the blame for any problems from outside observers.
This is why for example, I see fancy CICD pipelines covering for static component dependencies locked into a hard coded version of components. Completely breaking a core value proposition of the pipeline, but someone got the story points and moved on. It turns out that small task of putting the project into the pipeline should have been decomposed further. Oops.
This philosophy is a power tool and like any such tool, you take care in where you point it, and it will serve you well. Point it in the wrong direction however, and it will also happily blindly eviscerate you with no malice.