Re-Engineering Legacy Software

Summary

As a developer, you may inherit projects built on existing codebases with design patterns, usage assumptions, infrastructure, and tooling from another time and another team. Fortunately, there are ways to breathe new life into legacy projects so you can maintain, improve, and scale them without fighting their limitations.

About the Book

Re-Engineering Legacy Software is an experience-driven guide to revitalizing inherited projects. It covers refactoring, quality metrics, toolchain and workflow, continuous integration, infrastructure automation, and organizational culture. You'll learn techniques for introducing dependency injection for code modularity, quantitatively measuring quality, and automating infrastructure. You'll also develop practical processes for deciding whether to rewrite or refactor, organizing teams, and convincing management that quality matters. Core topics include deciphering and modularizing awkward code structures, integrating and automating tests, replacing outdated build systems, and using tools like Vagrant and Ansible for infrastructure automation.

What's Inside

• Refactoring legacy codebases
• Continuous inspection and integration
• Automating legacy infrastructure
• New tests for old code
• Modularizing monolithic projects

About the Reader

This book is written for developers and team leads comfortable with an OO language like Java or C#.

About the Author

Chris Birchall is a senior developer at the Guardian in London, working on the back-end services that power the website.

Table of Contents

PART 1 GETTING STARTED
1. Understanding the challenges of legacy projects
2. Finding your starting point
PART 2 REFACTORING TO IMPROVE THE CODEBASE
3. Preparing to refactor
4. Refactoring
5. Re-architecting
6. The Big Rewrite
PART 3 BEYOND REFACTORING—IMPROVING PROJECT WORKFLOWAND INFRASTRUCTURE
7. Automating the development environment
8. Extending automation to test, staging, and production environments
9. Modernizing the development, building, and deployment of legacy software
10. Stop writing legacy code!