Cognitive Debt
In this episode of Beyond the Stack, Michael explores a form of exhaustion that has nothing to do with workload or productivity. It’s the kind that comes from replaying moments that are already over.
A meeting that ended hours ago.
A decision that’s already been made.
A comment that landed the wrong way.
Everything has moved on, but internally, you’re still there.
Using a classic Zen koan and a modern software engineering analogy, this episode introduces the idea of Cognitive Debt: the mental and emotional load we carry when an experience is technically resolved, but not internally integrated.
Much like technical debt, cognitive debt doesn’t always hurt right away. But over time, it increases mental load, shortens patience, and quietly destabilizes individuals and teams.
This episode isn’t about breaking rules or ignoring standards. It’s about noticing what you’re still carrying, and understanding how ego, identity, and “should vs shouldn’t” thinking can distort clarity long after the work is done.
Key Topics Covered
A Zen koan about letting go after the moment has passed
The modern engineering version of the story: rules, exceptions, and hotfixes
Why replaying closed situations creates hidden mental load
The difference between resolving work externally vs internally
“Should” and “shouldn’t” as arguments with reality
How cognitive debt quietly accumulates in professional environments
The relationship between cognitive debt and burnout
Why unresolved internal tension often masquerades as professionalism or virtue
Awareness as a professional skill, not a personality trait
Key Reflections from the Episode
The most damaging work often happens after the work is done
Not all exhaustion comes from effort. Some comes from resistance
Cognitive debt is a loan against your future mental capacity
The longer something goes unintegrated, the more interest it accrues
Ego doesn’t always show up as arrogance. Often, it shows up as unfinished internal work
Questions to Sit With This Week
What professional moment do you keep replaying long after it ended?
What decision did you accept outwardly but resist internally?
Where are you enforcing a rule inside yourself that no longer applies to reality?
If you’re not the one bearing the consequences, why are you still carrying the weight?
Episode Theme
Cognitive Debt
The mental load created when we borrow against our attention by arguing with reality instead of integrating it.
Resources & Related Work
Beyond the Commit: The Human Side of Software Development
More reflections and essays on Michael’s Substack: beign13.substack.com
Previous episodes of Beyond the Stack exploring awareness, ego, and team dynamics
Closing Thought
The crossing ended at the river.
The bug was fixed in production.
The work moved on.
Only one person kept carrying the weight.
What are you still carrying?
