56K views · Dec 13, 2019 · 44:46 · 1 HN recommender · 3 mentions · discussed 2021–2022
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 Hacker News points people here: Cited as a practical approach to finding the technical debt that matters, and as a reference for codebase visualization.
“I think Adam Tornhill has a nice take on this.”HN comment, 2021
“I think Adam Tornhill has a nice take on this.”
Focus on high-complexity, high-churn areas rather than quantifying tech debt.
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
“There are several public conference talks that cover this visualization and related use cases”
Conference talks covering codebase visualization and related analyses.
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
Listed among resources on program architecture.
principlkes of chaos engineering : link unix as an ide : link using ed : link editor articles : link pioritizing technical debt : this video
