Technical debt gets talked about like weather. Something that happens to you. Something that accumulates in the dark, between the good intentions and the deadline.

It isn’t. Not usually.

Most of the time, someone made a call. Maybe they said it out loud, maybe they didn’t. Maybe they told themselves it was temporary. But there was a moment — a real moment — where a slower, harder path was available, and a faster, cheaper one was taken instead.

That’s not a condemnation. Tradeoffs are the work. The problem isn’t the choice. The problem is the amnesia that follows it.


Tolkien understood this better than most management books. In the Second Age, Celebrimbor poured his skill into the Rings of Power with genuine intent. He wanted to preserve, to create, to give the Elves something that could hold back the entropy of the world. The craft was real. The desire was real. But the speed at which Sauron worked alongside him, the urgency to achieve the vision, meant the foundation was compromised before the spires were raised. The Rings were not corrupted by laziness. They were compromised by a craftsman who didn’t slow down long enough to ask: why is this going so smoothly?

The most dangerous technical debt isn’t the ugly kind. It’s the elegant kind. The abstraction that almost works. The shortcut that seemed reasonable at the time and now holds a critical path together.


Epictetus had a clear way of thinking about this. The only things within your control are your judgments and your actions. Not the deadline someone else set. Not the pressure from above. What you control is whether you name the tradeoff honestly, whether you write it down, whether you track the cost.

Debt acknowledged is debt that can be managed. Debt denied compounds in silence.

I’ve seen teams spend months pretending the foundation was solid while the build accumulated weight. Every sprint added a floor. No one wanted to be the one who stopped to say: this structure has a problem. So they kept building. Fast. Confident. Toward collapse.


The stoic move isn’t to refuse all shortcuts. That’s rigidity dressed up as principle. The stoic move is to see clearly. To choose with open eyes. To say: we are taking this debt, for these reasons, and here is what we owe ourselves by Q3.

That kind of honesty requires psychological safety. It requires a team culture where “I cut a corner” isn’t an admission of failure but the beginning of a conversation. Where the post-mortem isn’t a trial.

Most teams don’t have that. So the debt hides. And it earns interest.


The question isn’t whether to take shortcuts. Sometimes the right call is to ship and fix it later. The question is whether you’re the kind of team that actually fixes it later — or the kind that writes “// TODO: clean this up” and ships the TODO alongside the feature, forever.

If you wrote that TODO six months ago, when did you plan to pay it back?