Every big project contains a section of indispensable, incomplete, and incomprehensible code.
Careers rise and fall working on it, and the product lives or dies according to its quality. In this article, John Farrell suggests practical steps for revising, refactoring, and rebuilding bad code so that it performs the functions required of it, and becomes good code that you're proud to maintain. By following these steps, you can save the project and become a well-paid, respected team player with a corner office, without losing your sanity or working late. It's 50,000 lines of the oldest code on the project. The authors have left the company and won't return your calls.