Episode Summary

For decades, software engineers quietly learned to measure their value (both professionally and personally) by how much code they produced. Commits, pull requests, velocity, and visible output became proxies for competence, trust, and worth.

But that mental model is starting to break.

In this episode of Beyond the Stack Podcast, Michael explores how this belief formed, why it worked for so long, and what happens when the very craft that once created security begins to act as a constraint. With the rise of AI-assisted development and increasing pressure for speed and efficiency, engineers are being forced to confront a deeper question:

What happens when the work that makes you valuable becomes invisible?

This is not an episode about tactics, tools, or career hacks. It’s a reflection on identity, value, and the human side of engineering work that rarely gets named—until it starts to hurt.

What This Episode Explores

* Why writing code quietly became a stand-in for professional worth

* How businesses learned to value visible output over invisible thinking

* The unintended consequences of anchoring identity to implementation

* Why AI didn’t create this tension, but made it impossible to ignore

* How fear, urgency, and “productivity” distort how engineers respond to change

* What it means to move beyond proof-of-work toward proof-of-thought

* How to make judgment, context, and decision-making visible without becoming a target

Key Moments & Themes

* The craft as identity — when specialization turns into confinement

* Visibility vs. value — why what matters most is often hardest to see

* AI as an accelerant — changing the scoreboard, not the game

* Trauma responses at work — fight, flight, freeze, and fawn in engineering culture

* The Post-Implementation reality — when implementation is no longer scarce

* Proof-of-thought — making thinking legible in systems that reward output

Who This Episode Is For

* Software engineers who feel productive but unsettled

* Senior engineers whose work feels harder to explain than it used to

* Developers navigating AI without clear language for what’s shifting

* Anyone sensing that “doing more” no longer resolves the discomfort

A Reflection to Carry With You

How much of your most valuable work happens in places no system is designed to see?

And what happens to your sense of worth when that work remains invisible?

If this episode resonates, you’re not alone. These questions show up, again and again, across teams and careers, often long before anyone gives them words.

This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit peign13.substack.com