







Technical Debt is a metaphor for the consequences of cruft. You either have to accept a drag on further features (paying interest) or fix the software (paying the principal)
How Generative and Agentic AI Shift Concern from Technical Debt to Cognitive Debt
The term technical debt is often used to refer to the accumulation of design or implementation choices that later make the software harder and more costly to understand, modify, or extend over time...

Organizational Debt is Like Technical debt — But Worse
Startups focus on speed since they are burning cash every day as they search for product/market fit. But over time code/hardware…


AI is Accelerating our Social Debt — Development Seed
Open source communities need to pay down social debt with the same urgency we give technical debt.

Technical debt as a lack of understanding
Some time back, I was working on a project where it felt like the timebomb of technical debt was exploding in our faces. We couldn’t refactor the whoositz because of the whatsitz and when we asked about the whatsitz no one knew about the whatsitz and how it exactly worked with the whoositz and there certainly weren’t tests for it. When we notified management they replied, “We’re in a build the plane while flying situation, how can we get this out now without doing a big rewrite?” It was pretty clear how the technical debt had amassed.
Conceptual Debt is Worse than Technical Debt
Definition. The consequences of making bad design choices when choosing concepts to model your product around. A conceptual or mental model…
Unpacking the Mechanics of Conduit Debt Financing
Understanding the pass-through financing model behind the AI infrastructure boom

Tech debt metaphor maximalism
I really like the "tech debt" metaphor. A lot of people don't, but I think that's because they either don't extend the metaphor far enough,...
Prompts are technical debt too
It’s common and correct to say that “all code is technical debt”. Adding code is a necessary evil for developing new features: you almost always have to do it, but each line of code adds to the complexity and maintenance burden of the system. All future changes to the system have to work with the existing code, or at least avoid breaking it. Once systems accumulate enough code, they become impossible for a single person to understand: instead of reading the code and understanding what it does, you must rely on guesses, theories and heuristics1. Sensible engineers write as little code as possible.

A Taxonomy of Tech Debt
Hi there. I’m Bill “LtRandolph” Clark, and I’m the engineering manager for the Champions team on LoL . I’ve worked on several different teams on League over the past years, but one focus has been consistent: I’m obsessed with tech debt. I…

Five US tech giants' hidden debts soar to $1.65tn on opaque AI funding
Data center leases, GPU supply contracts raise liabilities at Meta, Oracle, Nikkei study shows

Research Debt
Science is a human activity. When we fail to distill and explain research, we accumulate a kind of debt...
Investors dump data centre bonds as AI borrowers face ‘Darwin moment’
Debt issued by AI infrastructure providers and neocloud companies such as CoreWeave has sunk to increasingly stressed levels

AI Companies Are Trying to Hide a Staggering Amount of Debt
AI companies are pouring tens of billions of dollars into enormous data centers. They're being built on top of a mountain of hidden debt.

You’re Not Taking On Enough Tech Debt
TL;DR - The cost of servicing technical debt is plummeting because of LLMs; assuming coding models keep improving. You're better off taking more technical de...
