7 minute read

There’s a specific kind of tired that’s been going around lately. Not burnout exactly. Not the good kind of tired you get after actually finishing something. It’s more like the feeling after a long flight where you’ve been quietly alert the whole time, bracing for turbulence that never quite arrives. You land and somehow you’re exhausted from sitting still.

If you work anywhere near technology - or honestly, just exist online - you probably know the feeling. The constant stream of model releases. The breathless announcements. The LinkedIn posts from people who seem to be running entire companies with a single prompt, while you’re still trying to figure out why the AI confidently gave you directions to a restaurant that closed five years ago.

This is AI fatigue. It’s a real thing, it’s widespread, and if you’re feeling it, you’re in good company.

What It Actually Looks Like

AI fatigue doesn’t always show up in an obvious way. It tends to show up sideways.

Actual physical tiredness. Literally tired. Genuinely drained after spending a few hours trying to get a tool to do what you need it to do.

A background hum of anxiety. Am I falling behind? Should I be using this more? Am I going to be irrelevant in two years?

Frustration that tips into anger. Angry at the tools, at the hype, at the “AI thought leaders” smugly announcing that the AI will be doing 100% of your job by next week, at the people who seem to find all of this completely effortless.

Guilt or shame. I should be further along with this. Other people are building entire apps. I can barely get it to format a table correctly.

Disappointment. This was supposed to be a leap forward,it was supposed to make my life easier. What you got was a tool that can draft a strategy memo but can’t tell you how many r’s are in ‘strawberry’.

If some of that sounds familiar, you’re not alone in it.

Good News: You’re Not the Problem

One thing that helped me was realising this might not be a personal failing.

Human beings are not built for rapid, continuous, unpredictable change. We’re wired for a world that changed slowly; seasons, not software releases. Our nervous systems are finely tuned to detect threats and novelty, and when the environment keeps shifting faster than we can adapt, the brain doesn’t just shrug and carry on. It activates the part of our brain responsible for keeping us alive and triggers a low-level stress response. A continuous background wariness; stay alert, something might matter here. This is genuinely exhausting, not to mention unhealthy. Psychologists call this hypervigilance. It’s useful when you’re on the lookout for predators. Not so much when the threat is a new frontier model dropping every six weeks.

And then there’s everything else.

There is just so much to learn. Prompting. Agents. RAG. Governance. Context windows. Fine-tuning. Each of these is a real field, not a weekend tutorial. Our brain has a working memory limit, and we’ve all been asked to absorb an extraordinary amount in a very short period of time. Of course it’s tired.

“Am I going to lose my job?” Even if your role isn’t under any immediate threat, the constant ambient noise of AI will replace X by Y registers somewhere deeper than rational thought. Threats to livelihood and social standing light up the same circuits in the brain as physical danger. That low-level chronic stress doesn’t feel dramatic from the inside. It just feels like unease you can’t quite shake.

The endless choosing. Claude or GPT? Gemini or something open source? Do I need to learn to code? What even is an MCP? Every week brings a fresh set of decisions about tools and approaches that simply didn’t exist two years ago. None of them feel urgent individually, but the cumulative weight of constant choosing is real, and it quietly depletes the same mental reserves you need for everything else.

You open your feed and immediately see: “I’m running 5 businesses with 100 AI agents.” Then someone’s 47-step prompt that apparently prints money. Then a hot take about which jobs will be gone by Thursday. The gap between what they seem to be doing and what you’re doing feels huge, even when the gap is mostly fiction.

“I used to actually make things. Now I just review them.” This one is subtle, but a lot of people feel it. As AI handles more of the first-draft work - the writing, the initial designs, the code - your role quietly shifts toward reviewing, editing, and evaluating. That sounds like less effort. It often doesn’t feel that way. There is something genuinely satisfying about making something from scratch, and something quietly draining about spending your day assessing what a machine produced. The creative spark gets replaced by a red pen, and that’s a real loss worth recognizing.

None of this means you’re doing it wrong. It means you’re a human being responding to an environment that isn’t particularly designed for human beings.

The Environment Isn’t Helping Either

The pace of your own adaptation isn’t actually the main problem. The information environment around AI is overwhelming.

Announcements from AI companies are, almost without exception, marketing. A new model release is a product launch dressed up as a news event. The influencer pipelines built around AI content are monetized on anxiety and engagement; the more unsettled you feel, the more you click. The people making pronouncements about which professions will be obsolete by next quarter are almost never the people doing those jobs.

You can’t realistically keep up with all of it. In fact, trying to keep up with all of it might be one of the least productive things you can do right now.

What’s Actually Helped

I don’t have a clean system for this. These are just some things that have made it feel more manageable.

Picking a lane for a while. Not permanently. Just long enough to stop the constant internal negotiation about whether I should be doing something else. It helps to just decide, even temporarily. For the next three months, I’m going to focus on learning one thing and not worry about the rest. Or even: I’m going to sit this particular wave out and check back in six months. Both are legitimate choices. What drains you is the not-deciding.

Accept that mastery here is genuinely hard. AI is not one skill. It’s a landscape that includes prompt engineering, agentic systems, retrieval, security, governance, and domain-specific applications, each of which is itself a significant learning area. You cannot learn all of it. Nobody can. The goal is useful knowledge.

Start embarrassingly small. Start with something that feels almost too small to bother with. Ask an AI to help you draft one email you’ve been putting off. Use it to summarize one long document. Don’t try to rebuild your workflow in a weekend. Small wins add up, and more importantly, they rebuild the sense of agency that fatigue erodes.

Give yourself permission to be a beginner. You are learning a genuinely new category of tool, in real time, without a curriculum, while also doing your actual job. Of course you don’t have it figured out yet. Nobody does, even if their Insta or LinkedIn suggests otherwise.

Pick one small project that’s actually yours. The learning that sticks tends to be attached to something you care about. Something low-pressure and personally interesting. A simple budgeting tool. A recipe organiser. A journaling app. Build something small and see what you can do. The point isn’t the output. It’s rebuilding a relationship with the tools that’s based on curiosity instead of obligation.

Find people learning at your pace. Not the people posting highlights. People who are confused sometimes, delighted sometimes, figuring it out as they go. That kind of community makes the whole thing bearable.

Be more selective about what you pay attention to. You don’t have to mute everything, but it’s worth being deliberate. Company announcements are marketing. Social media posts are highlight reels. The most useful signal tends to come from people who are doing real work with these tools and talking honestly about what’s working and what isn’t.

The Honest Version

AI is a real technological shift. It’s moving fast. Your discomfort with that isn’t a character flaw or a skills gap. It’s a reasonable response to an unfamiliar rate of change.

You don’t have to learn everything. You don’t have to feel great about all of it. You don’t have to be doing more than you’re doing.

You just have to figure out what’s actually useful for you — at a pace that doesn’t burn you out.

It’s also probably the only pace that works.

Updated: