1 HN user recommended this talk1 month2021–2022score 1
Years with an HN recommendation, 2007–2026
Cited as a practical approach to finding the technical debt that matters, and as a reference for codebase visualization.
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.
“I think Adam Tornhill has a nice take on this.” (HN, 2021)
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 [this video]
Focus on high-complexity, high-churn areas rather than quantifying tech debt.
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: [this video]
Conference talks covering codebase visualization and related analyses.
Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.
Plays via YouTube's privacy-enhanced embed
3 Hacker News comments
From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.
Citations, criticism and jokes