Technical Debt is a catch-all term that we use for entropy in software development. Systems grow, become unruly, and difficult to work with. When this happens, we often know that we can do better, but it is hard to take concrete actions which help us get a strong a sense of control over the evoluton of an entire code base.

This is material beyond what Michael outlined in his classic book "Working Effectively in Legacy Code." It is more focused on large scale change.

Please note that places are limited so book now to avoid disappointment!

• Identify various types of technical debt
• Assess the amount of technical debt in your codebase
• Develop design plans for large-scale refactoring and debt mitigation
• Alter team and organizational process to make refactoring a first-class practice

During this two-day Masterclass, Michael will outline what he has learned about managing change in large code bases over time.

Topics covered include:

• A Pragmatic Definition of Technical Debt
• Design Decision Cards
• Feature Probes
• Scratch Refactoring
• Design Direction Tagging
• Limited WIP Refactoring
• Design Quality Trend Analysis
• Systematic Refactoring/Rewriting