Maintaining a legacy application can make you feel like mice in a maze. In this article Ping Chen shares her experiences on how to pragmatically maintain a large legacy application. "Pragmatic” is the operative word; since a legacy application can have lots of technical debt, one has to be strategic in choosing the right battles.
You've just started working on a large Java application. How would you go about understanding the code base? In a typical enterprise Java team, most of the senior developers who can help you are likely to be quite busy. Documentation will be sparse. You will need to quickly deliver and prove yourself to the team. How would you resolve such a situation? This article offers some suggestions.
Even Java systems can be "legacy" systems. This article explores 8 quick and relatively low risk ways to breathe new life into previously written-off Java applications. 5
Andreas Kaltenbach explains how MSDS solves backward software programs compatibility problems by negotiating the differences between versions to ease the upgrading process. 4
Using logging seams you can easily create unobtrusive unit tests around legacy classes, without needing to edit class logic as well as avoiding behavior changes. 3
Take a BAT to the legacy code you inherit: Build, Automate, Test. Jared Richardson shows how to create a safety net, to ensure that your code continues to work the way you want it to. 19