liveBook · Manning

Technical debt

As explained in Grokking Software Architecture

Technical debt is the future cost of short-term software design or implementation compromises made in favor of speed over quality and maintainability.

Technical debt is the future work and cost created by short-term design or implementation compromises made for speed instead of quality and maintainability. Like a loan, a shortcut may save time now but require repayment later—with interest. section 1.2 section 2.2

Taking on debt is a tradeoff, not automatically a mistake. Weigh immediate user and business value, deadlines, and how easy the solution will be to fix or extend. Choose deliberately rather than chasing a perfect design or shipping a shortcut blindly. section 1.2 section 2.2

A missed configuration update

A heater specification changed from 28 volts to 65 volts, but thermostat switches in one module were not updated. They melted shut during testing; the buried change had passed unit tests but later failed in production. section 7.6.1

Figure 1.1 An architect constantly faces a choice between the fast, messy path (Option A) and the slower, cleaner path (Option B). Making a deliberate, defensible decision is a core architectural skill.

Compare the fast, messy option with the slower, cleaner one; the choice should be deliberate and defensible. section 1.2

How Grokking Software Architecture covers it

How deep it goes
Defines future costs, explains repayment, and illustrates how an outdated configuration can cause a production failure.
Examples
Uses spaghetti code, a rushed delivery choice, and thermostat switches left unchanged after a specification update.
What you can do after
Evaluate shortcuts by weighing business needs, deadlines, maintainability, and measurable results.
How it connects
Connects technical debt to software architecture, maintainability, tradeoffs, and legacy code.

Also explained in

Compare how 16 books explain technical debt →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.