BT
rss
  • Pragmatic Techniques for Maintaining a Legacy Application

    by Ping Chen on  Jan 02, 2014 9

    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.

  • Refactoring Legacy Applications: A Case Study

    by Chen Ping on  Feb 27, 2013 7

    To refactor legacy code, the ideal is to have a suite of unit tests to prevent regressions. However it's not always that easy. This article describes a methodology to safely refactor legacy code.

  • Tips to Developers Starting on Large Applications

    by Choudary Kothapalli on  Mar 26, 2012 8

    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.

Eight Quick Ways to Improve Java Legacy Systems

Posted by Tim Cull on  Jul 26, 2010

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

Staying Safe and Sound Thanks to MDSD

Posted by Andreas Kaltenbach on  Feb 25, 2009

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 for Legacy Code Unit Testing

Posted by Ian Roughley on  Aug 01, 2006

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

Dealing with Legacy Code

Posted by Jared Richardson on  Jun 12, 2006

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

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2013 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT