How to deal with spaghetti legacy code
At least three times in my career as a programmer, I had to work on huge, complicated code written by other people. In one case I was specifically hired to replace the original maintainer who -as I later learned- left the company from a burnout caused by the frustration of having to maintain his own code. Inheriting legacy code is common, and few people enjoy it. Here I put down a few ideas that I think might help to deal with the situation....