"Never take down a fence until you understand why it was put up."
I used to use that one a lot with developers trying to improve on a predecessor's code...
"Never take down a fence until you understand why it was put up."
I used to use that one a lot with developers trying to improve on a predecessor's code...
That's also why rebuilding systems from scratch (the old "just rip it all out and do it again") usually doesn't work: there is a great deal of wisdom, however poorly implemented or documented, buried within that system. Starting over abandons those minute but critical bits, and must be re-discovered the hard way.
However, the world and the society we live in is changing so quickly (technology, cultural mixing, global warming, you name it) that the new norm for changing the rules is not generations but years or months. Using Facebook? Change your settings today or lose your entire life history to strangers! and so on.
"Conservatism is about respect for established institutions!"
"But every conservative I see is running around tearing down those institutions."
"Those people aren't real conservatives!"
I know because I share your approach. Having worked with a great many legacy / inherited systems, most with little or no documentation, and rarely with much in the way of contact with the system designer, it's a bit of an occupational hazard.
Sometimes you've just got to blow down the fences to see what happens. Sometimes it's nothing, sometimes it's the end of the world.
Fortunately, in technology, resurrecting fences is generally fairly straightforward, but not always.
That said, the worst fences are the ones you take down without realizing they were there ... which turn out to be critical.
"I don't know why this is here and I've tried to find out but hit a dead end so I'm getting rid anyway" is better than "I don't know why this is here so I'm just getting rid".
[1] - "all due respect" has also been stripped of proper meaning, relegated to a barely-veiled insult.