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.Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.About the BookRe-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 InsideRefactoring legacy codebasesContinuous inspection and integrationAutomating legacy infrastructureNew tests for old codeModularizing monolithic projectsAbout the ReaderThis book is written for developers and team leads comfortable with an OO language like Java or C#.About the AuthorChris Birchall is a senior developer at the Guardian in London, working on the back-end services that power the website.Table of ContentsPART 1 GETTING STARTEDUnderstanding the challenges of legacy projects Finding your starting pointPART 2 REFACTORING TO IMPROVE THE CODEBASEPreparing to refactorRefactoringRe-architectingThe Big RewritePART 3 BEYOND REFACTORING—IMPROVING PROJECT WORKFLOWAND INFRASTRUCTUREAutomating the development environmentExtending automation to test, staging, and production environmentsModernizing the development, building, and deployment of legacy softwareStop writing legacy code!
Author: Chris Birchall