Managing Architectural Debt in a Hypergrowth Context
summary
The talk explains architectural debt — the portion of technical debt coming from system architecture — and how it accumulates in hypergrowth companies due to technical, organizational, and human causes. It presents a practical framework developed at the presenter’s company to define and measure architectural debt, and discusses how measuring it enables targeted refactorings or larger transformations; the work builds on research by Roberto Verdecchia, Antonio Martin and EADebts.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:34What is technical debt
- 6:51Architectural debt defined
- 11:14Causes and consequences
- 15:27Debt management theory
- 22:54ManoMano’s approach
- 25:20Identifying existing debt
- 34:06Prioritization and visibility
- 37:37Key points and conclusion
- 41:30Q&A
related talks
46mManaging architectural debt in a hypergrowth context
45mYou Thought Technical Debt Was the Worst? Meet Design Debt!
28mManaging Technical Debt at Scale
57mPutting an end to "technical debt"
35mTechnical Debt. A guide for developers and IT managers
01h 03mLong-lived software architectures that survive decades without debt
31mDealing with Technical Debt
45mA developer always pays his debts