What it takes to make legacy code bases rock solid

Another thing I realized last year is that next to building green-field projects (who doesn’t like that?), I really love working on legacy code bases and making them rock solid. It’s so rewarding to take something that was in production successfully but is suffering from all kinds of technical issues (and the resulting team productivity issues) and make it better, release by release.

Things (in no particular order) that I typically spend time on (although it all highly depends on the state, the goals, the needs, the culture, etc.):

• Talk to the people to understand the biggest pain points, both from a user perspective, product management perspective and developer perspective
• Establish principles and conventions for coding, naming, testing, design, documentation, source control and refactoring principles
• If there’s no test coverage, introduce Characteristic Tests as a temporary safety net and then gradually introduce appropriately scoped automated tests.
• Refactor code and create architectural and design-level seams to make it more testable and allow more isolation in the team
• Introducing a clean build pipeline so what you build and deploy locally as you would in production
• Setting up a clear branching and…