> Here, I propose Scott’s Law: never put order in a system before you understand the structure underneath its chaos.
Previously formulated as Chesterton's Fence [0], among others.
There's definitely a blind spot in software for the general principle that you should understand a thing well before you decide to remove it. Anyone want to propose some theories on why disregard for an extant body of work tends to plague software so extensively?