Chesterton’s fence as applied to software: don’t replace a bad software solution until you understand why it is that way. Still, looking back we can see how so

Chesterton’s fence as applied to software: don’t replace a bad software solution until you understand why it is that way. Still, looking back we can see how software solutions were not optimal for their age, and how amazing things can be coaxed out of old hardware using new insights. It would be pretty remarkable that precisely now is when we finally achieved optimal software. More likely, we’re still getting it wrong, and this is just one more step along the line. The truth can be a little of both: yes, we can do better than what exists now, but we’re not guaranteed to unless we understand what came before.