You're Not Alone.
Communities for AI-Fatigued Engineers
One of the cruelest parts of AI fatigue is the silence. You look around your Slack, your standups, your conference talks — and everyone seems fine with it. Excited, even. It can make you feel broken. You're not. Here's where to find the others.
Why community matters when you're already exhausted
Fatigue is partly cognitive. But a significant part of what keeps it going is narrative isolation — the feeling that your experience isn't real, isn't valid, or isn't shared.
When everyone around you seems to be thriving with AI tools — shipping faster, interviewing better, building side projects in weekends — and you're quietly losing your sense of craft, something insidious happens. You don't just feel tired. You start to feel wrong.
The antidote isn't always more information or more techniques. Sometimes it's just hearing someone else say: "Yeah. Me too. This is real."
"Social support is one of the strongest moderators of burnout. Isolation amplifies occupational stress — not because community fixes the root cause, but because shared meaning-making reduces the psychological load of carrying an experience alone."
— Adapted from Maslach & Leiter, Burnout: The Cost of Caring
This page is a map. It's not a prescription. You don't need to join everything — you need to find one or two places where you can be honest, and where the people around you will understand what you mean when you say "I just don't feel like the code is mine anymore."
Why engineers suffer in silence about AI
Before we get to where to find community, it's worth understanding why so many engineers haven't found it yet.
Fear of looking behind
If you admit you're struggling with AI tools, you risk being seen as someone who can't keep up. In an industry that prizes cutting-edge, "I'm not sure this is good for me" can feel career-limiting.
The enthusiasm performance
Engineering culture often rewards visible enthusiasm for new tech. Many engineers privately have doubts but perform excitement in public. It creates a cascade of silence where everyone thinks they're the outlier.
Lack of vocabulary
"AI fatigue" is a relatively new term. Without language, it's hard to Google, hard to describe to a friend, hard to bring up in a 1:1. People feel the thing but can't name it — which makes it harder to seek support.
Remote work isolation
A distributed team means fewer casual conversations, fewer moments where someone leans over and says "I'm struggling too." The informal support structures of physical workplaces just don't exist in async environments.
Understanding these barriers is step one. The communities below are places that have, in various ways, created permission to have the honest conversation.
Online communities worth your energy
A note on how to use this list: you don't need to be active everywhere. One community where you feel genuinely heard is worth ten where you lurk anxiously. Start as a reader. Comment when something resonates. Connection builds from specificity, not volume.
Reddit communities
r/ExperiencedDevs
Highest signalThis subreddit explicitly focuses on mid-career and senior engineers. AI fatigue, skepticism about tooling, and questions about craft are discussed openly here. The culture actively pushes back against hype. Best for: senior engineers, craft concerns, "am I alone in this?" moments.
Filter by "AI" or search "AI fatigue" — there are dozens of threads going back two years.
r/cscareerquestions
Broad but realMore junior-to-mid, but genuinely honest about fears. Imposter syndrome threads, questions about AI's impact on junior roles, and anxiety about the market — all here. Less moderated than ExperiencedDevs but more volume. Best for: early-career, market anxiety, "what does this mean for my job?" questions.
r/devops, r/sysadmin, r/devops
Domain-specificAdjacent communities where AI fatigue manifests differently — around infrastructure, automation anxiety, "the runbook that nobody reads anymore." Best for: ops engineers, SREs, platform engineers.
r/ArtificialIntelligenceSkeptic (and similar)
Use with careAI skeptic communities can be validating, but watch the vibe. Some skew toward doomerism or contrarianism that can deepen anxiety rather than relieve it. Useful for finding language and community; less useful if the negativity spirals reinforce rumination. Take what's useful, leave what isn't.
Hacker News
HN isn't a community in the traditional sense, but certain thread types reliably surface honest conversations about AI fatigue. Search for: "AI fatigue," "vibe coding," "I miss writing code," "copilot makes me worse," or "skill atrophy."
The comment threads on these can be some of the most honest writing on the web about what AI tools are actually doing to senior engineers. You won't make friends there, but you'll find evidence you're not alone. That counts for something.
Lobste.rs
Invite-only, heavily moderated, and deliberately slower than HN. The culture actively resists hype cycles. Engineers who've burned out on tool-of-the-month culture often migrate here. If you can get an invite (ask a current member), it's one of the most thoughtful tech communities on the internet.
Dev.to
Mixed quality, but the honest personal essays about burnout and AI overwhelm get real engagement here. Less competitive than Medium, more personal than HN. Writing your own story here — even a short post — can be surprisingly therapeutic and draws more empathy than you might expect.
Discord servers worth knowing
In-person connection: why it hits different
Online communities are real. But there's something different about sitting across from another engineer and having the conversation in person — seeing the recognition on their face, the small nod when you say something true.
If you can get there, in-person connection around these topics tends to be more healing than digital-only engagement. Here's how to find it.
Local meetups
Search Meetup.com for "developer," "software engineering," or "tech" in your city. Many have a small honest-talk culture you won't find at big conferences. The trick: show up consistently for 2–3 events before expecting depth. Relationships build over time.
If your city's meetups are all sales pitches and job hunting, consider starting a "craft-first" one. You'll be surprised how many engineers show up.
Unconferences & barcamps
Unconferences (attendee-driven agendas) are where the honest conversations happen. Software Craftsmanship UK, various Agile Open events — these attract engineers who want to talk about how they work, not just what's new. Smaller than traditional conferences, higher signal.
Slow-coding clubs
A small but growing movement of engineers who meet to code deliberately, without AI tools, on problems they find interesting. Often organized through Meetup or locally within companies. Sometimes called "notebook coding" or "craft sessions." If none exists near you, consider starting one.
Retreats & sabbaticals
Some engineers are finding that a few days away from screens — a tech retreat, a meditation retreat, a cabin with friends — is the reset that digital-only approaches couldn't provide. Radical Rest retreats for tech workers are an emerging category worth exploring.
"One of the most surprising findings in burnout recovery research is how quickly a single genuine in-person connection can shift someone's assessment of their own situation. Not because the situation changed — but because the meaning around it did."
— Field notes from occupational health research on remote worker isolation
How to actually show up in community when you're depleted
Here's the thing: when you're most exhausted is often when community feels most impossible. Showing up in a new space takes energy you don't have. So let's be practical.
Start as a reader, not a contributor
You don't have to post. Lurking is valid. Reading threads that resonate — feeling understood from a safe distance — still helps. Give yourself permission to receive without giving anything yet.
One upvote, one reaction, one reply
The smallest act of engagement — upvoting a comment that says what you feel, reacting with 💯 to a post that articulates your experience — can be the beginning. It tells your nervous system: I exist here. I'm allowed to be here.
Write your story (even if no one reads it)
The act of writing out your experience — what happened, when it started, what it feels like — is therapeutic independent of audience. Posting it and getting responses is a bonus. The real work is naming the thing. Our private journal is a safe place to start.
Find one person, not a crowd
Community doesn't have to mean a thousand members. One colleague, one Slack friend, one online acquaintance you can be honest with — that's enough to start dismantling the isolation. Think: who in my life might understand this if I tried to explain it?
Bring a specific question or experience
"I'm burned out" is hard to respond to. "I've noticed I feel hollow when I push code that Copilot largely wrote, and I don't know if that's rational" is specific enough to get real engagement. The more precise your language, the more likely you are to find resonance.
Protect your energy from toxic positivity
Some communities, when you say "I'm struggling with AI tools," will respond with "have you tried X tool?" or "you just need to learn to use it better." That's not support. Know when to disengage from people who can't sit with the honest experience.
Starting the conversation at work
External community is valuable. But your immediate environment — your team, your manager, your skip-level — shapes your daily experience the most. Sometimes the most healing thing is finding one honest conversation at work.
Some openers that have worked for engineers:
With a peer you trust
"I've been feeling a bit weird about how much AI is in my workflow lately. Like, I'm shipping more, but I'm not sure I'm actually getting better. Have you had any of that?"
In a 1:1 with your manager
"I want to flag something that might just be me adjusting, but I've been noticing some friction around my AI tool usage — not the output quality, more around engagement and feeling connected to the work. I'm still figuring out how to describe it, but I wanted to mention it."
In a team retro or async channel
"Anyone else want to do a low-key retrospective on how we're actually feeling about AI in our workflow? Not the output metrics — more like the experience of using it day to day? I've been curious what others think."
You don't need everyone to agree. You just need to signal that it's okay to be honest — and often, two or three people will quietly reply "actually, yeah."
For more on workplace conversations, see our workplace AI fatigue guide and the manager's guide to AI fatigue.
The Clearing: a space for this exact conversation
This site exists because a few engineers needed it and couldn't find it anywhere else. We built it as a sanctuary, not a product. No tracking. No accounts. No ads. No gamification.
Right now, The Clearing is a collection of resources, tools, and honest writing. But the community is growing — in newsletter inboxes, in forum DMs, in conversations that people have told us started with "I read something on this site and forwarded it to my team."
The Dispatch
A weekly letter from engineers who get it. No hype. No growth-hacking. Just honest thinking.
Subscribe →Private Journal
Write without an audience. Process what's happening. No one else reads this.
Write →Take the Quiz
Name what you're feeling. Share your result with a colleague who might need to see it.
Take it →When community isn't enough
Community is powerful. But it's not a substitute for professional support when things have crossed into clinical burnout, depression, or anxiety disorders.
Some signs that you might need something beyond community forums:
- You're not sleeping, or sleeping too much, for more than a few weeks
- The feelings of dread or hollowness follow you outside of work — weekends, mornings before you open your laptop
- You're isolating from friends and family, not just professional peers
- You're having thoughts about harming yourself or not wanting to exist
- Substance use or other coping behaviors have increased
If you need immediate support
- US: Crisis Text Line — text HOME to 741741
- US: 988 Suicide & Crisis Lifeline — call or text 988
- UK: Samaritans — 116 123 (free, 24/7)
- Global: findahelpline.com — locate your country's resources
Burnout occupational therapists, tech-specialized therapists, and coaches who work with engineers are also an underutilized resource. They understand the specific texture of engineering culture — the identity investment, the imposter syndrome, the always-on expectation — in a way that general practitioners sometimes don't.
See our recovery guide for more on when to escalate.
Frequently asked questions
Yes. Spaces like r/ExperiencedDevs, the Lobsters community, certain Dev.to circles, and craft-focused Discord servers have genuine conversations about AI's downsides. The Clearing's own community is built specifically around this conversation. The field is still young but growing fast — searching "AI fatigue" or "AI burnout" on any major platform now returns real results.
It depends on your team culture. Many engineers find it safer to start in anonymous or pseudonymous online communities before bringing these conversations to the workplace. Once you've found your language and normalized your own experience, it becomes easier to have the conversation with managers or peers. Our workplace guide has conversation scripts for various situations.
You're probably not — but others may not feel safe saying it. Research shows that many engineers are privately skeptical about AI tools but feel pressure to appear enthusiastic. Finding community outside your team first can help you feel less isolated. Then, when you're more grounded, it becomes easier to gently surface the conversation with a trusted colleague. You might be surprised how quickly someone says "yeah, actually."
Avoid framing it as anti-AI. Lead with your experience, not a critique of the tools. "I've been feeling a loss of craft satisfaction" lands better than "AI is ruining programming." Most enthusiasts have doubts too — you may unlock a real conversation. It also helps to find a specific, concrete moment: "I finished a feature last week and realized I couldn't explain 40% of the code. That felt strange to me."
Venting releases pressure but doesn't create change. Actual support involves being heard, having your experience normalized, getting practical ideas, and sometimes being gently challenged. Good communities do both: they let you breathe, and then they help you move. If you find yourself venting to the same people repeatedly without it shifting anything, that's a sign to seek something with more structure — a coach, a therapist, or a deliberately developmental community.
That's completely valid, especially when you're deep in fatigue. Introverts often recover best with solitary practices first — journaling, walking, reading, building something slow and deliberate for yourself. The Clearing's tools — the journal, check-in, and decompress pages — are designed for solo recovery. Community can wait until you have more energy for it. There's no obligation to process collectively.
Keep exploring
Engineer Stories
Real accounts from engineers who've been there. You'll recognize yourself.
🌱Recovery Guide
Practical, phased recovery for engineers at different stages of fatigue.
🏢Workplace Guide
How to set limits and have honest conversations with your manager.
📓Private Journal
Write privately. Process what's happening. Nothing leaves your browser.
🧩Your Engineer Type
4 archetypes of AI-fatigued engineers. Which one are you?
💌The Dispatch
A weekly letter for engineers finding their way back. No spam. Unsubscribe anytime.