Software archaeology

A nice note about how to deal with legacy systems:

“Mitch Rosenberg of InfoVentions.net, Inc. claims that the first law of software archaeology (he calls it code or data archaeology) is:

Everything that is there is there for a reason, and there are 3 possible reasons:

  • It used to need to be there but no longer does
  • It never needed to be there and the person that wrote the code had no clue
  • It STILL needs to be there and YOU have no clue

The corollary to this “law” is that, until you know which was the reason, you should NOT modify the code (or data).”

Leave a Reply