Technical Neglect
summary
Argues that technical neglect — the absence of upkeep and attention — causes the drag labelled as technical debt, not the reverse. Cites measurements: about 31% of org tech is legacy, 60–80% of IT budgets go to keeping it running and 88% of businesses feel the drag. Tests of AI refactoring show raw LLM output only ~37% successful while a fact‑checked pipeline raises valid refactors to ~98%. Recommends change in processes: continuous “clear as you go”, measured repayment, and tooling plus human verification.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:36Debt misattributed as cause
- 7:11Boat metaphor for legacy
- 16:22Maintenance vs project thinking
- 22:02Metaphors and limits
- 28:00Legacy code definition
- 34:03Cost of legacy systems
- 43:10AI code as new legacy
- 51:17Why debt metaphor fails
- 56:57Consequences of unmanaged debt
- 1:02:17Failure demand costs
- 1:06:15Neglect shaping codebases
related talks
52mTechnical Neglect
34mThe Technical Debt Trap
35mTechnical Debt. A guide for developers and IT managers
28mTechnical Debt: Why it'll ruin your software
39mTechnical debt isn't technical
25mDemystifying Technical Debt
49mDług techniczny - skryty oprawca organizacji nie tylko technologicznych
26mTech debt as innovation, reframing this forever problem as an opportunity