hackertube.io

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

GOTO Conferences · talk · Watch on YouTube

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

What it is

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 recommends it

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

  • 1 people recommended it
  • 1 different months
  • 0 strong recommendations
  • first 2021, last 2022

What HN commenters said

  1. “I think Adam Tornhill has a nice take on this.”

    Focus on high-complexity, high-churn areas rather than quantifying tech debt.

    clumsysmurf, 2021-01 · Recommendation · in “Code Age vs. Time to Recall”

Excerpts from Hacker News comments, linked to the originals. Summaries and labels were written by a language model from those comments.

Topics: technical debt, code hotspots, code churn, software evolution, code analysis

Also recommended by the same people