HackerTube.runGood videos, with context.
Prioritizing Technical Debt as if Time & Money Matters • Adam Tornhill • GOTO 2019
About this video
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.
Why it appears in the archive
Cited as a practical approach to finding the technical debt that matters, and as a reference for codebase visualization.
AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.
From the Hacker News discussion
I think Adam Tornhill has a nice take on this. He recommends tech debt not be quantified as such, but encourages focusing on areas with high complexity and large churn GOTO 2019 • Prioritizing Technical Debt as if Time and Money Matters • Adam Tornhill [VIDEO]
Read original comment ↗That's a great visual presentation, but not really an innovation. The CodeScene tool has that built in together with a set of deep analyses on top (see [LINK] ). There are several public conference talks that cover this visualization and related use cases: [VIDEO]
Read original comment ↗principlkes of chaos engineering : [LINK] unix as an ide : [LINK] using ed : [LINK] editor articles : [LINK] pioritizing technical debt : [VIDEO]
Read original comment ↗