Prioritizing Technical Debt as if Time & Money Matters • Adam Tornhill • GOTO 2019
GOTO Conferences
Why leaders watch it
Shows how to prioritize technical debt by combining code complexity with change frequency instead of arguing about estimates.
Adam Tornhill's GOTO Copenhagen 2019 talk on how to prioritize technical debt in large codebases. It argues for combining code complexity with change frequency (hotspots) from version control data, rather than trying to quantify debt in the abstract.
Takeaways
- Prioritize debt where complexity and churn overlap
- Use data to justify refactoring work
- Not all debt is worth paying down
Topics: Engineering & technical leadership, Focus & prioritization
Related
- Debt Metaphor · Ward Cunningham
- Days to Seconds: Harnessing Confidential AI Agents with Kellie Romack · Opaque Systems, Inc.
- AWS re:Invent 2019: Optimizing Aerospace manufacturing operations & supply chain with AWS (MFG201) · AWS Events
- Software Engineering's Greatest Hits · Greg Wilson
- Software Art Thou: Glenn Vanderburg - Real Software Engineering · Zendesk
- Agile is Dead • Pragmatic Dave Thomas • GOTO 2015 · GOTO Conferences
- Kellie Romack on how ServiceNow Generated $355M in AI Value | Technovation 1062 · Metis Strategy
- Does AI Actually Boost Developer Productivity? (100k Devs Study) - Yegor Denisov-Blanch, Stanford · AI Engineer
- #NoEstimates (Allen Holub) · Allen Holub
- Leadership, Culture, and Ethics in Cybersecurity · Dr. Mansur Hasib - #DrCybersecurity
- How Agentic AI Changes The Workplace — With Jacqui Canney and Kellie Romack · Alex Kantrowitz
- Kellie Romack on ServiceNow's $355M AI Transformation | From 4 Days to 8 Seconds · CAIO AI Leadership Podcast