Episode 4 / Jan 24, 2026

Sunk cost, AI deniers, and Elon talks with Jesus

Sunk cost in the AI era: John and Eric define the bias, share candid stories, and show how identity, tech debt, and market shifts demand pivots, reality checks and the freedom of starting over.

Take it with you

Listen on your platform

Spotify ↗Apple Podcasts ↗Substack ↗

Listen here

The conversation in writing

Show notes

Summary

John and Eric unpack the sunk cost fallacy through personal stories, clean definitions, and why it intensifies in fast-moving AI and software. They contrast stubbornness-as-craft with market reality, show how identity and ego can cloud pivots, and offer practical checks: external feedback, tighter problem framing, and willingness to start over.

Key takeaways

Name the bias: Prior investment should not drive future investment. Always optimize for present and future ROI, not the past.
Identity check: Notice when a project becomes “part of me,” because that’s when impartial judgment collapses.
Use outside calibration: Ask trusted, domain-relevant peers to sanity-check your assumptions.
Accept utilitarian wins: AI-produced code may be inelegant, yet commercially superior. Tests and agents will raise quality anyway, so it’s time to accept the future of software development.
Freedom is willingness to start over: If you can let go of valuable things and start from zero, you won’t run the risk of getting bogged down by sunk costs.

Noticeable mentions and links

Sunk cost fallacy is defined as the bias of using prior investment (time, money, effort) to justify continued investment, even when it impairs present decision-making.
Thinking, Fast and Slow, written by Daniel Kahneman, is referenced for its System 1 / System 2 lens to explain why sunk cost can feel emotional and irrational.
Steam-powered boats and the Morse code/telegraph are cited as cases where stubborn persistence eventually met enabling tech, highlighting survivorship bias.
The "rich young ruler" story from Matthew 19 in the Bible is used to illustrate identity attachment and how letting go of things core to oneself can be the real barrier to change.
Elon Musk, via Walter Isaacson's biography, is referenced as an anti–sunk-cost archetype, repeatedly risking everything and switching when needed.
Benn Stancil's framing (LLMs read fast and summarize "roughly") is echoed to explain why AI coding feels transformative: machines don't slow down on code reading/writing.

Every word of the conversation

Transcript

Find a word or phrase

Studio (00:01.691) Welcome back to...

Welcome back to...

That was my speakers on. No worries. We'll have to, I'm going to restart that. You can, or you can just trim the beginning too. I'll just trim it. I'll just trim it. retake two. Here, I'll mark the clip.

Studio (00:21.019) Welcome back to the Token Intelligence Show. Today we have a short, and I brought the topic last time, which was the woes of AI chat interface. And John, today you are bringing a topic around sunk cost. And so you've done a bunch of thinking about this. I've done a very little bit of thinking about this. So let's just jump right in. Sunk cost, especially as it relates to AI. Where did this idea come from?

Welcome back to the Token Intelligence Show. Today we have a short, and I brought the topic last time, which was the woes of AI chat interface. And John, today you are bringing a topic around sunk cost. And so you've done a bunch of thinking about this. I've done a very little bit of thinking about this. So let's just jump right in. Sunk cost, especially as it relates to AI. Where did this idea come from?

First off, think we have to address the elephant in the room. Yes. that shorts for us might not be shorts for our listeners. Short means it's probably less than 60 minutes. than an hour. Yeah. Okay. So Sankost. So this, this has just been, it's just, there's, I think you're like this too. There's the topics that they come up and then they come up again in your mind and come up again in your mind. So that's been one of mine for the last like couple of months. Yes.

Related conversation / Episode 35

7 questions with Trey Grainger: AI is an alien intelligence, not a computer

AI has transformed how we find information, and Trey Grainger literally wrote the book on how that happened. John asks him 7 questions about his career and AI.

Explore this episode ↗

Token Intelligence

The conversation

Summary

Key takeaways

Name the bias: Prior investment should not drive future investment. Always optimize for present and future ROI, not the past.

Identity check: Notice when a project becomes “part of me,” because that’s when impartial judgment collapses.

Use outside calibration: Ask trusted, domain-relevant peers to sanity-check your assumptions.

Accept utilitarian wins: AI-produced code may be inelegant, yet commercially superior. Tests and agents will raise quality anyway, so it’s time to accept the future of software development.

Freedom is willingness to start over: If you can let go of valuable things and start from zero, you won’t run the risk of getting bogged down by sunk costs.

Noticeable mentions and links

Sunk cost fallacy is defined as the bias of using prior investment (time, money, effort) to justify continued investment, even when it impairs present decision-making.

Thinking, Fast and Slow, written by Daniel Kahneman, is referenced for its System 1 / System 2 lens to explain why sunk cost can feel emotional and irrational.

Steam-powered boats and the Morse code/telegraph are cited as cases where stubborn persistence eventually met enabling tech, highlighting survivorship bias.

The "rich young ruler" story from Matthew 19 in the Bible is used to illustrate identity attachment and how letting go of things core to oneself can be the real barrier to change.

Elon Musk, via Walter Isaacson's biography, is referenced as an anti–sunk-cost archetype, repeatedly risking everything and switching when needed.

Benn Stancil's framing (LLMs read fast and summarize "roughly") is echoed to explain why AI coding feels transformative: machines don't slow down on code reading/writing.