HackerTube

Prioritizing Technical Debt as if Time & Money Matters • Adam Tornhill • GOTO 2019

GOTO Conferences1 HN recommenders · 2021–2022
56K views · talk · evergreen · Uploaded 2019-12-13

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.

Cited as a practical approach to finding the technical debt that matters, and as a reference for codebase visualization.

Software practice, open source & careersTesting, debugging & developer toolsSoftware architecture & design

Watch on YouTube

3 comments from Hacker News

@clumsysmurf2021 · in “Code Age vs. Time to Recall”

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]

RecommendsView on HN
@nephrenka2021 · in “Show HN: Visualizing a Codebase”

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]

CitesView on HN
@sargstuff2022 · in “Ask HN: Resources/discussions about program architecture”

principlkes of chaos engineering : [LINK] unix as an ide : [LINK] using ed : [LINK] editor articles : [LINK] pioritizing technical debt : [VIDEO]

CitesView on HN