March 2018
Intermediate to advanced
276 pages
7h 11m
English
Now that we’ve seen how multifaceted technical debt is, it’s time to discuss what we can do about it. Given this interaction of technical and organizational forces, how do we uncover the areas in need of improvement? Ideally, we’d need the following information:
Where’s the code with the highest interest rate? In case we have some subpar code—and which large system doesn’t?—we need to know to what degree that code affects our ability to evolve the system so that we can prioritize improvements.
Does our architecture support the way our system evolves? We need to know if our architecture helps us with the modifications we make to the system or if we have to work against our own architecture.
Are ...
Read now
Unlock full access