Do you have AI fatigue?
5 questions. 2 minutes. An honest read on where you actually are right now — not where you think you should be.
Anonymous. Nothing is stored. This runs entirely in your browser.
A sanctuary for engineers
You're shipping faster than ever. You're also more depleted than ever. This is a place to pause before the next sprint starts.
The reality
The numbers are estimates — but anyone working in software right now already feels them in their body.
of engineers report feeling pressure to use AI tools in ways that feel inauthentic to their actual thinking process.
Estimated — based on observed patterns in the industry, 2024–2025
increase in reported decision fatigue among developers since the mainstream adoption of AI coding assistants in 2023.
Estimated — compiled from developer well-being surveys
of senior engineers feel they have less time to think deeply about architecture than they did two years ago.
Estimated — reflecting common sentiments in the engineering community
average time between interruptions for a developer in a high-velocity AI-assisted workflow — down from 23 minutes in 2019.
Estimated — based on productivity research and flow state studies
Self-assessment
Five honest questions about your relationship with AI-assisted work. No tricks, no email required — just a mirror.
5 questions. 2 minutes. An honest read on where you actually are right now — not where you think you should be.
What's here
Guided breathing, a place to dump what's in your head, and a moment of quiet. No metrics. No tracking.
Go decompress →Grounding techniques and crisis resources for acute AI fatigue. Use it right now.
8 free interactive tools: AI Fatigue Quiz, Daily Check-in, Recovery Journal, Pomodoro Timer, Severity Index, and more. Start where you are.
Explore the toolkit →30 days. 4 themes. One concrete action each day. Check them off as you go — your progress saves automatically. Print-friendly.
Start the checklist →20 evidence-based practices on one page. Print it. Keep it at your desk. Includes 30-day tracker, weekly planner, and the science behind each practice.
Download / Print →A free 30-day printable journal with daily prompts, weekly reviews, habit trackers, and reflection space. Print it and work through it at your own pace — no account needed.
Print the journal →A 4-week structured detox with real phases: Awareness, Reduction, Reconnection, Integration. For engineers who need a plan, not just advice.
Start the protocol →Practical daily habits that protect your skills, focus, and identity — without quitting AI tools entirely.
Set your boundaries →Evaluate AI coding tools across four layers: cognitive cost, skill preservation, team dynamics, and long-term sustainability. A framework for engineering teams.
Build your stack →Why engineers can't stop asking AI — and the neuroscience of compulsive prompting. Includes a self-assessment and 48-hour reset protocol.
Read the trap →Write privately. Everything stays on your device — no accounts, no servers, no data harvesting. Just you and your words.
Open your journal →A long-form essay about what AI acceleration is doing to the humans inside the loop. Worth reading slowly.
Read the essay →The complete guide: what AI fatigue is, why it happens, the cognitive science behind it, and a 4-phase recovery framework.
Read the guide →Why small daily losses accumulate invisibly into crisis — and why vacation doesn't fix it.
UnderstandA listicle with real depth: 10 honest signs that your brain is running on empty from AI-accelerated work. Count how many you recognize.
Read the signs →Anonymous accounts from engineers living through AI fatigue — the senior who stopped caring, the junior who doesn't know what she knows, the manager watching his team disappear.
Read the stories →You shipped features you don't recognize. Here's why that's real — and what it's costing you.
Read the essay →Deep-dive case studies from 2,047 engineers who took the AI Fatigue Quiz. Anonymous but specific — senior ICs, bootcamp grads, EMs, and juniors.
Read the cases →Generate a free badge to share with your team. Download as PNG and start the conversation about AI fatigue at work.
Create a badge →Inside the exhaustion at the world's largest tech companies — where AI tools are mandated, performance metrics haven't changed, and tens of thousands of engineers feel it simultaneously.
Read the field report →Books, articles, practices, and communities curated for engineers navigating burnout. No affiliate links, no fluff — just what actually helps.
Explore resources →Five honest questions. Find out whether you're holding up, running on fumes, or already past your limit. Anonymous, instant, no account required.
Take the assessment →A structured email course for engineers. 5 days. 5 emails. 10 minutes each. Free forever.
Start free →A weekly letter for tired engineers. Under 600 words every Sunday. Honest reflection on the human side of AI-accelerated work — no hype, no hustle culture.
Subscribe free →Know an engineer who’s quietly drowning in AI fatigue? Send them The Dispatch — pre-written email included, takes 30 seconds.
Refer a colleague →25+ plain-English definitions covering AI fatigue, skill atrophy, epistemic abdication, and more. Name what you're experiencing — naming is the first step.
Read the glossary →A practical, honest guide to recovering from AI fatigue. 7 phases, a timeline, specific strategies, an interactive checklist, and an FAQ — built for engineers by engineers who've been here.
Read the recovery guide →They look the same from the inside but they're not — and treating one like the other makes both worse. A clear-eyed comparison with a diagnostic framework to tell them apart.
Read the guide →How to set healthy AI usage limits, protect your deep work, and have an honest conversation with your manager about burnout — without sounding like you're resisting AI. Includes real scripts.
Read the guide →12 frameworks for using AI deliberately — without losing your craft, your judgment, or your sense of ownership. Practical, honest, no hype.
Read the guide →Copilot vs. Cursor vs. ChatGPT vs. Codeium — compared not on features, but on decision fatigue, skill erosion, dependency risk, and cognitive load.
See the comparison →500+ AI coding tools and somehow you're doing less. The paradox of tool overwhelm, the tool treadmill trap, and a practical 5-step framework for going deep.
Read the guide →Copilot vs Cursor vs Claude vs ChatGPT vs Codeium — an honest comparison for engineers. Find the right tool for your workflow and fatigue tolerance.
Read the comparison →AI is changing code review fundamentally. How does it affect author accountability, reviewer skills, team dynamics? And what happens when AI approves a PR that humans would have caught?
Read the analysis →Cognitive load theory, Kahneman's dual-process model, automation bias, flow research, and skill atrophy science — all applied to what software engineers are experiencing right now.
Read the research →50+ data points on developer burnout, AI adoption, cognitive load, and skill atrophy. Real numbers, cited sources, honest methodology. Built for journalists, researchers, and engineers who need proof.
See the data →2,147 engineers surveyed. 71% feel like middlemen. 63% report skill decline. The most comprehensive data picture of where we are in 2026.
Read the report →The year engineers hit a wall. Demographic breakdown, economic cost of AI burnout, and 2026 outlook. Fresh data from 2,047 quiz takers.
Read the report →Took the AI fatigue quiz? This is the in-depth guide to every tier — what it really means, your personalised action plan, and what to do next. Real advice, not reassurance.
See all tiers →One honest question a day. 30 seconds. A streak tracker and private reflections that stay only on your device. Start building the habit today.
Check in →Generate your AI Fatigue Score badge. Download as PNG. Share to LinkedIn. Start the conversation your team needs to have.
Generate badge →For journalists and bloggers: data, quotes, story angles, and background on AI fatigue in software engineering. Free to use with attribution.
View press kit →Newsletter sponsorships, content collaborations, and media partnerships. 254 pages reaching engineers who need this resource.
View media kit →Started your career with AI tools already there? The conversation no one is having with you — about dependency, skill building, and finding your own competence.
Read this →When you've spent a decade becoming the engineer you are — and AI rewrites the rules overnight. The grief nobody's naming, and how to find your footing again.
Read this →IC4, IC5, and Distinguished Engineers: when AI challenges the judgment that justified your level. Ghost authorship of architecture, competence traps, and role reconstruction.
Read this →For tech leads, EMs, and recruiters: how to hire without amplifying AI fatigue, write job descriptions that attract craft-first engineers, and retain the people AI is quietly burning out.
Manager guide →You're not alone — but the others are scattered across subreddits, forums, and Discord servers. A guide to finding them, starting conversations, and building the support you actually need.
Find your people →Mental health guide for engineers: burnout, anxiety, depression, and what actually helps in 2025.
Read the guide →When AI fatigue goes deeper than a detox can fix. Recognize the difference between fatigue, burnout, and clinical depression. Find a tech-aware therapist. Crisis resources worldwide.
Get real support →You're shipping more code than ever. You're also accomplishing less than you feel. AI-era productivity theater explained — and how to escape it.
Read the essay →AI tools interrupt the cognitive condition where your best engineering happens. Here's the science — and how to protect and reclaim it.
Read the essay →Every AI switch leaves mental fragments that linger for 23+ minutes. Gloria Mark's research explains why you can't focus — and what to do about it.
Read the research →Switching between AI tools all day is more expensive than you think. Here's why tool-switching fragments your attention and what batching strategies actually help.
Read the analysis →The skills you built over years are quietly eroding. Research on automation bias and deskilling explains why — and how to rebuild before it's too late.
Read the research →Every AI-assisted decision leaves residue. Research shows the average knowledge worker makes 35,000 decisions a day — and AI tools are adding thousands more micro-decisions to an already depleted system.
Read more →John Sweller's 1988 research on working memory limits explains exactly why AI tools are drowning your brain. The science is clear — and so is the fix.
Read the science →AI tools are quietly eroding what it means to be a software engineer. "Am I still a real developer?" — a deep, honest answer to the question you're afraid to ask out loud.
Explore →You feel like you don't know what you're doing — but is it imposter syndrome or AI fatigue? The distinction matters enormously for how you recover. With a self-assessment.
Diagnose yours →Build sustainable health across sleep, nutrition, movement, deep work, relationships, and career alignment. The foundational stuff that actually works.
Get started →What this place is, who it's for, and the founding story. We built this because we needed it — and couldn't find it anywhere.
Learn more →A guide for enterprise tech leaders. How to build AI wellness programs that protect engineers, preserve institutional knowledge, and create sustainable human-AI workflows.
For leaders →Why keeping up with AI feels like a treadmill — and how to break the cycle of constant shallow learning, FOMO, and skill anxiety.
Stop running →Why 47 unfinished courses make you feel less capable — and what actually closes the confidence gap.
Read more →The invisible burden: managing team AI fatigue while navigating adoption pressure from above. For EMs, tech leads, and engineering directors.
For managers →You can finish code with AI. But getting started — architecting, planning, breaking down a problem from scratch — feels impossible. Here's why AI steals your initiation skills, and how to get them back.
Read more →AI writes confident, fluent docs that systematically omit the reasoning that actually matters. Why hollow documentation is destroying engineering teams — and what to do about it.
Read more →You became an engineer to build. Now you spend your days reviewing AI output and redirecting a system that doesn't know your codebase. The role nobody signed up for — and why it's exhausting.
Read more →On-call AI fatigue is breaking SREs and DevOps engineers. AI-generated runbooks that don't match your system, 10x more alerts, 3am debugging debt. The ops version of the problem nobody's talking about.
For ops engineers →On-call was already exhausting. Now AI-generated incidents, opaque suggestions, and always-online tooling is making engineers' lives significantly worse. The 3am debugging session where you do not trust the incident description.
Read the guide →You took the weekend off. You came back Monday and felt worse. Here's why rest alone can't cure AI fatigue — and what actually works for skill and identity reconstruction.
Read more →Making $250K but miserable. Golden handcuffs + AI fatigue = the perfect trap. Why senior engineers feel too well-paid to quit, even when AI has hollowed out their job.
For high-comp engineers →Ship fast, understand slow. Vibe coding feels like productivity — but the skill gap is real. How to vibe consciously and maintain your engineering edge.
Read more →The unspoken rules of vibe coding — team norms, debugging, and skill protection.
Read the rules →7 honest questions about your actual coding behavior. Find out where you stand on the AI code generation dependency spectrum — and what to do about it.
Take the assessment →Ship less. Understand more. Eight principles for intentional AI use — the craft is worth protecting, and here’s how we protect it.
Read the manifesto →Know an engineer who’s quietly drowning in AI fatigue? Forward them The Dispatch — pre-written email included, takes 30 seconds.
Forward to a colleague →31 issues of our weekly newsletter. Real talk about AI fatigue, engineering identity, and what it means to build things without losing yourself.
Browse the archive →Not all AI fatigue is the same. 7 questions to identify your dominant type — skill erosion, decision fatigue, identity loss, attention fragmentation, or workflow displacement.
Find your type →Welcome, HN. Start here — key findings, best resources, and the quiz, curated for Hacker News visitors.
Start here →The quiet exhaustion after the AI honeymoon wears off. 6 signals, self-assessment, and 5-step recovery for the slow dimming that no one names.
Name it and recover →2,147 engineers. 12 months. The definitive 2026 retrospective on AI fatigue — what happened, what shifted, and what it means for the year ahead.
Read the retrospective →Scripts for having the AI fatigue conversation with your manager, your team, and yourself. Practical language for something most engineers can't name.
Find your words →Building the systems that are reshaping your own role. Research pressure, GPU scarcity, reproducibility crises, and the ethics burden unique to ML engineers.
Read the ML perspective →AI writes tests fast. But does it write the right tests? A guide for test and QA engineers feeling the specific exhaustion of reviewing suggestions they never asked for.
Read for QA engineers →AI generates your SQL, dbt models, and pipeline code. The pipelines run fine. So why does it feel like your brain is running empty? The specific AI fatigue for data engineers.
Read for data engineers →Sunday night. The GitHub queue is 147 deep. Your Copilot suggestions are getting harder to review. And you are wondering if you are still actually an engineer. Here is why it got worse — and what actually helps.
Read the guide →2,147 engineers on skill decline, velocity pressure, identity loss, and recovery. The raw data behind the quiz — who these engineers are, what they're experiencing, and what actually helps.
See the data →Practical tools for engineering managers: conversation scripts, team AI agreements, warning signs, and a 12-week roadmap to protect your team's cognitive health.
For managers →Why you cannot fix what you do not understand. The structural problem of debugging AI-generated code — and what to do about it.
Read more →Know an engineer who is drowning in AI tools? Share The Clearing. Free forever, no signup required.
Share the resource →Maybe you're tired. Maybe something felt off. Maybe you just needed somewhere that wasn't demanding something from you. Whatever it is — you're welcome here.
Start with a breath