Chapter 6. Technical Debt and Architecture

In this chapter, we explain how to recognize technical debt at the architectural level. We introduce lightweight structural analysis techniques that you can apply to the code or the design to help identify and understand design decisions that lead to technical debt.

Beyond the Code

In Chapter 5, “Technical Debt and the Source Code,” we showed how the accumulation of small deficiencies in the code can lead to a substantive amount of technical debt, which can in turn make forward progress harder, more costly, and more error prone. But there is increasing evidence that the most expensive technical debt is related to the architecture of the software system—and it is harder to pay back. The effective management ...

Get Managing Technical Debt: Reducing Friction in Software Development now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.