March 2018
Intermediate to advanced
276 pages
7h 11m
English
Part I provided the basic tools to prioritize technical debt. Now we scale those concepts to work at an architectural level to gain insights into the system as a whole. You’ll see how the same techniques help us build new code as we use the information proactively to counter potential problems before they become maintenance issues.