Share Your AI Fatigue Story

You've been carrying something heavy. The feeling that you're losing something you built over years — your skills, your confidence, your sense of what you're actually worth as an engineer. You're not alone in this. And your story could be exactly what another engineer needs to read today.

Your story matters. We publish real stories from engineers at every level — anonymously or by name. Every story we publish receives messages from engineers who finally felt understood. Sharing takes 10 minutes.

What Engineers Are Sharing

Every story is different. These are the themes that come up most often.

Most common

Losing the craft feeling

"I used to feel the pride of solving something hard. Now I finish tasks and feel nothing. I don't know if I actually built anything or just approved AI output."

Very common

The identity crisis

"I'm 12 years into this career and I don't recognize myself as a developer anymore. My manager keeps saying I'm doing great. I feel like I'm disappearing."

Common

Junior engineers left behind

"I graduated bootcamp 2 years ago and I still don't feel like I actually know how to code. AI fills in everything I should be learning, and I can't tell what's me and what's the tool."

Common

Senior engineers watching decline

"I used to mentor junior devs. Now I watch them delegate everything to AI and I don't know how to talk about what's happening without sounding like a crank."

Common

Mandatory AI adoption

"My company mandated Copilot for everyone. I was already tired. Now I'm tired and confused about what I'm actually good at."

Common

Recovery attempts that didn't work

"I tried taking weekends off. I tried no-AI Fridays. Nothing sticks. I feel like I'm managing a slow leak I can't find."

Submit Your Story

Use the prompts below or write freely — whatever feels natural. You control your anonymity.

Prompt 1 — The turning point
Prompt 2 — What it costs you
Prompt 3 — What you've tried
Prompt 4 — What you want others to know
We never publish your email or contact you without permission.

Your story is reviewed within 5 days. We never publish without your explicit approval of the final wording.

Story submitted — thank you.

We'll read your story carefully and reply within 5 days. If we think your experience would help other engineers, we'll reach out about publishing it.

🌿

Recovery Guide

Practical steps for AI fatigue recovery
💬

Testimonials

Stories from engineers who found their way back
📬

The Dispatch

Weekly stories + recovery insights

Frequently Asked Questions

Yes. Many engineers choose to share anonymously — first name, initials, or 'Anonymous Engineer' are all fine. We never publish identifying information without your explicit permission. You control what we know about you.
You don't need to be a writer. We have a simple prompt-based format that makes sharing easy. If you want to submit a longer free-form story, that's welcome too.
Yes. Every story we publish receives emails from engineers who say it was the first time they felt understood. The most powerful stories aren't polished — they're honest.
Any genuine AI fatigue experience: craft erosion, identity crisis, skill loss, recovery attempts, manager conversations, layoff aftermath, junior engineer struggles, senior decline, team dynamics.
Yes. If you'd rather share privately through the newsletter read by 2,000+ engineers every week, submit through the newsletter form and note 'for The Dispatch only.'
We read every submission. If your story is selected, we'll email you within 5 days to confirm wording and anonymity preferences. You get final approval before anything goes live.

Other Ways to Connect

💬

Read Testimonials

Engineers share what recovery actually looked like for them
🤝

Community Hub

Find online communities, in-person groups, and peer support
📋

Take the Quiz

See where you fall on the AI Fatigue Spectrum
📬

The Dispatch

Weekly stories and recovery insights in your inbox