The Wheel Spins Faster: AI Ambition and the Health Tax Nobody Talks About

Last week alone, I was running Claude Code agents on three codebases, researching different protocols, testing new model releases, shipping a feature for a real client, writing about all of it, and somehow also being a CTO.

I didn't have this many parallel tracks before AI. Not even close.

The wheel spins faster, and I run faster, and somehow it still feels like I'm falling behind.

I think it's the curiosity that does it. Every new tool opens four new rabbit holes. Every agent you build makes you want to build two more.

And nobody warns you about the health tax.

The Productivity Illusion

Here's the thing nobody says out loud: AI didn't give us more free time. It gave us more ambition.

Before AI, I could build one feature in a day and feel good about it. Now I can build three, and the voice in my head asks why it wasn't five. The goalpost moves every single week because the tools get better every single week.

And it's not just me. Look around. Every builder I know is running the same race. More repos, more side projects, more newsletters, more experiments. The people who were already driven are now driving themselves into the ground.

The tools are supposed to help. And they do. But they also create a new kind of pressure that didn't exist two years ago: the pressure of knowing what's possible.

When you know an AI agent can draft your emails, scaffold your app, and research your market in the time it takes to eat lunch, eating lunch starts to feel like waste.

That's the trap.

The Comparison Problem

Then there's the other side of it. Competing with others who are completing the same goals.

You see someone ship a full SaaS product in a weekend thread. You see a solo founder announce they replaced their entire engineering team with Claude Code. You see a 22-year-old who just built something in three days that took your team three months last year.

And you think: I should be doing more.

This is the new flavor of comparison. It's not about who has the better car or the bigger office. It's about who shipped faster, who automated more, who figured out the new model before you did.

It's a competition where the finish line moves backward every time you get close to it.

The honest truth is that most of those threads don't show the burnout, the skipped meals, the 2am debugging sessions, the relationships put on pause. They show the demo video and the launch tweet.

You're comparing your behind-the-scenes to everyone else's highlight reel. Except now the highlight reels are AI-accelerated too.

The Body Keeps Score

Your brain might be able to context-switch between three codebases and a client call and a research rabbit hole. Your body cannot.

Here's what I've noticed in myself when I'm deep in an AI-powered sprint:

Sleep goes first. You tell yourself you'll just run one more agent, check one more output, test one more prompt. The blue light keeps you wired. The dopamine of watching code generate in real-time is genuinely addictive. Suddenly it's 1am and your alarm is set for 6.

Then food gets weird. You skip breakfast because you're in flow. You eat lunch at your desk without tasting it. Dinner becomes whatever requires zero preparation, because cooking means stepping away from the terminal.

Movement disappears. Your step count drops. Your back starts talking to you. Your eyes burn by 4pm. You start thinking standing up counts as exercise.

And the subtle one: your nervous system stays activated. Even when you're not coding, your mind is running. You're thinking about the next feature, the next agent configuration, the next thing to ship. Your rest isn't restful because your brain hasn't gotten the signal that work is over.

The body keeps score on all of it. And it will send you the bill.

What I'm Actually Changing

I'm not going to pretend I've figured this out. I haven't. But I've started making changes because I've seen what happens when you don't.

First: hard stops. Not soft suggestions, hard calendar blocks. At a certain hour, the terminal closes. Not because I want to stop. I almost never want to stop. That's exactly why it has to be a rule and not a feeling.

Second: movement that isn't optional. I don't negotiate with myself about whether today is a gym day. The negotiation is where it falls apart. You put it on the calendar like a client meeting and you show up.

Third: I've started treating meals like infrastructure, not interruptions. If you're going to run your brain at high RPM for 10 hours, it needs fuel. Real fuel. Not another coffee and a protein bar at 3pm.

Fourth: I stopped trying to follow every rabbit hole the same day I find it. I have a list. Things go on the list. The list is long. That's okay. Not everything needs to be explored this week. The tools will still be there tomorrow.

And fifth, maybe the hardest one: I'm trying to stop measuring my day by output volume. Some days you ship three features. Some days you think clearly about one problem and that thinking prevents a month of wasted work. Both days count. The second one might count more.

The Real Competition

The person you're actually competing with is yourself six months from now. Not the person on Twitter who shipped faster. Not the AI influencer who claims they built a billion-dollar product in a weekend.

You. In six months.

And that person needs you to still be healthy, still be sharp, still be curious without being consumed. That person needs you to have slept, eaten real food, moved your body, and maintained the relationships that keep you grounded.

Burning out doesn't just cost you the week you crash. It costs you the three months of diminished capacity that follow. I've seen it happen. I've had it happen.

The fastest way to fall behind is to sprint so hard you can't run anymore.

A Note to Anyone Feeling This

If you're reading this and thinking "that's me," I want you to know it's not a personal failing. It's a structural problem.

The tools we have now were designed to increase throughput. They succeeded. But nobody designed the off switch. Nobody built the guardrails for human sustainability into the AI workflow.

That's on us to build for ourselves.

You're not lazy for taking a break. You're not falling behind by sleeping eight hours. You're not wasting potential by going for a walk instead of running another agent.

You're maintaining the system that runs all of it.

The wheel will keep spinning faster. New models will drop. New capabilities will unlock. The rabbit holes will multiply.

But you only get one body and one mind. And the best AI setup in the world is useless if the person operating it is running on fumes.

Take care of the machine that matters most. The one you can't replace with an API call.