How much do you pay for your legacy code? Many team spend up to 7/8 of their development budget on bugs, bug management and triage, late-added features, and so on. And that's on top of invisible costs - the cost to read hard-to-read code, the cost to test hard-to-test code, and the cost to communicate about arcane code. Let's change that.
This session demonstrates micro-skills, culture shifts, and organizational refactorings that dramatically reduce the cost to work with legacy code. We will show how real teams have reduced their cost to ship while reducing bug counts, in both the short-term and long-term simultaneously. The key: a whole different way to think about refactoring. And a whole different way to read, test, and talk about code. Learning Outcomes: