During my most recent performance review, I received a piece of feedback that has rapidly become the defining corporate koan of 2026: I am not using AI enough. I need to "find ways to better integrate AI into my day-to-day."
Naturally, I asked the obvious follow-up question: What, specifically, does that mean?
Which problems am I solving too slowly? Where is my architecture lacking? Which deliverables are falling behind because a stochastic parrot wasn't involved in the drafting process?
The response was a masterclass in hand-wavy middle-management improv. There were no specifics. There was no actual problem to solve. The tool itself had become the deliverable. In the upside-down logic of modern tech leadership, shipping clean, reliable, well-architected code is secondary to making sure you burn enough GPU tokens doing it so an executive can put a green checkmark on a quarterly board slide.
We have officially passed the phase where AI was pitched as a helpful assistant. We are now in the era of forced ideological compliance—and it is actively rotting the mental well-being of software engineers from the inside out.
The Burnout of the "AI Champion"
If you want to see where this mandate leads, don't look at the skeptics like me. Look at the true believers.
I recently had a quiet conversation with one of the biggest AI adoption champions on our team. This is the guy who did everything management asked. He drank the Kool-Aid, integrated the workflows, chained the prompts, and became the poster child for the "augmented engineer."
He is completely burned out. Worse than that, he told me he no longer feels any joy or sense of accomplishment in his work.
And why would he? For decades, software engineering was a craft. You wrestled with complex state machines, untangled gnarly race conditions, and designed systems in your head until the puzzle pieces clicked into place. That friction—the struggle of thinking deeply and building something deterministic out of pure logic—was the exact source of the dopamine hit when it finally compiled and passed the tests.
When you force engineers to become full-time prompt babysitters and glorified code reviewers for an overconfident hallucination engine, you strip away the craft. You replace the deep satisfaction of creation with the mind-numbing exhaustion of auditing. You get all the cognitive load of debugging someone else's messy code, with none of the pride of authorship, all while management expects 3x the output because "the AI writes it for you now."
We aren't automating away the drudgery to leave time for creative problem-solving. We are automating away the creative problem-solving and turning engineers into exhausted assembly-line inspectors.
The Unsupervised Bot in the China Shop
As if the psychological toll of babysitting LLMs wasn't enough, management is already itching to remove the babysitter altogether.
Just today, leadership proudly announced that a new bot has been let loose on our codebase to fix localization-related bugs unsupervised. They dropped this into our laps and actually asked, with a straight face, "What do you guys think about it?"
What do we think about an unthinking probabilistic script making unsupervised commits to localization strings and UI layouts? I think anyone who has ever dealt with string interpolation bugs, right-to-left layout breakages, context-dependent translations, or silent truncation issues knows how terrifying that is.
Who gets paged when that unsupervised bot subtly breaks a localized format specifier and crashes the app for an entire region? Not the bot. Not the VP who greenlit the bot to juice their "AI automation" metrics. The human engineers get paged. We are being asked to applaud the deployment of an automated chaos monkey while remaining 100% accountable for the wreckage it leaves behind.
Meditate for 20 Days, Win a Dystopian Blanket
Here is the cherry on top of this entire absurd sundae: it is currently "Mindfulness Challenge Month" at work.
At the exact same time leadership is telling us our organic human intellect isn't good enough on our performance reviews, hollowing out the joy of our craft, and unleashing unsupervised bots into our repositories, HR has swooped in with the ultimate cure for engineering burnout. If we log into an app and meditate for at least 20 days this month, the company will give us a free blanket.
You genuinely cannot parody this level of corporate dissonance.
We notice you're experiencing existential dread because we're devaluing your life's work and grading you on how enthusiastically you train your replacement. Have you tried box breathing? Do it twenty times and you can wrap yourself in this branded fleece while you fix the production regression caused by the localization bot.
Software engineers aren't burning out because we forgot how to breathe. We are burning out because we are trapped in a gaslighting factory where vague, top-down hype matters more than engineering reality, and where the joy of building things is being systematically crushed under a mandate to use tools that make us miserable.
Keep the blanket. Just let us write good code in peace.