Cruft and Technical Debt: A Long View
summary
Claim: cruft inevitably accumulates because external assumptions change faster than code, producing technical obsolescence distinct from intentional debt. Examples: jQuery builds a numeric-ID+cache workaround to avoid IE6 DOM memory leaks (it works but adds thousands of lines), Rails and Rack show when vertical integration or standardization reduces or shifts integration cost, Ember bets on client-side constraints that may erode. Concrete fixes: keep tests for legacy behavior, record assumptions in craft.txt or architecture docs, run periodic audits of APIs like jQuery DOM readiness to decide removals.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:29The Declining Value of Code over Time
- 3:23Open Source Ecosystem
- 21:37Who Pays the Integration Costs
- 27:26Example from Jquery
- 27:46What Does Jquery Do
- 34:41Rails
related talks
35mTechnical Debt. A guide for developers and IT managers
52mTechnical Neglect
25mDemystifying Technical Debt
31mAgility, Craftsmanship and Cargo Cult: What's the Link?
51mTechnical Debt as Theory Building and Practice
28mManaging Technical Debt at Scale
45mTechnical Debt: Taking back control when it's already messed up
49mDług techniczny - skryty oprawca organizacji nie tylko technologicznych