DEV Community

sgcdialler
sgcdialler

Posted on

Debugging/fixing a legacy application is like getting ready for work on a winter morning

You wake up and immediately trip over the dog. You apologize to the dog, get up off the floor, and stumble into the bathroom. (Open the project and the IDE claims everything is broken)

You start the shower, but there's no hot water. (Missing dependency?)

You check the water heater: the heating element is broken. You make a note to replace it, and go take a cold shower. (Referenced dependency version is out of date and unsupported--no time to test the latest version)

You finish washing up, and start getting dressed, and--oh, the cat puked in your good shoes. Fine, sneakers for today. (Deprecated framework call that made a function easy to understand--replaced with hacky but workable code)

You go downstairs and make a cup of coffee. This part goes just fine. (Persistence layer builds successfully. Hopefully everything else will work?)

You go out to the car. It starts. (Service layer builds and runs)
The garage door won't open. You manually open it. (firewall on your development machine blocked the service port--had to add an exception)

You drive to work, uneventfully (all test cases check out).

The doors are locked and no one is there. You call your manager who tells you that the whole area's power is out and won't be fixed for days--go home. Apparently you didn't get the company-wide text and email alert. (Project shelved until client fixes other infrastructure problems. No one told you until the project status meeting got canceled.)

Top comments (0)