Something rots in the developer brain, and nobody wants to name it.
I name it here.
The name is Token Anxiety. You wrote code in the last six months, so you felt it. It is a low-frequency hum behind your eyeballs. It is the itch to check a running agent while someone talks to you at dinner. It is the suspicion that a job could run right now, and it does not, and the fault is yours.
Let me explain.
The Old Buzz
Every programmer who codes long enough knows this feeling. You hit a wall. A bug or an architectural knot defeats your conscious mind. So you step away. You take a shower. You go for a walk.
Then the solution lands somewhere between the shampoo and the conditioner. The whole architecture clicks into place in one white flash.
That was the old buzz. It felt like a superpower.
The dark side was subtle. You sat at dinner, present in body and spiraling in your head. You felt the gears turn behind your ears even when you left the problem alone. Friends talk, the food goes cold, and half of you sits inside a function signature. Every long-time coder knows this feeling. It is intimate, and in a sick way it is almost romantic.
That buzz came and went. You had to earn it. A hard problem had to show up first.
The buzz is permanent now. It no longer comes from your brain.
It comes from the machines.
The Permanent Vibration
A culture takes shape among developers right now, and it unsettles me.
Someone leaves a party at 9:30 on a Saturday. Tiredness is not the reason. Illness is not the reason. They want to get back to their agents.
Nobody questions the exit. Half the room wants the same thing. The other half checks agent progress on a phone at the party.
Startup founders declare in public that they give up alcohol. They want a "maximally pristine" brain to "sling 10,000 lines of code a day." People say they replaced movies with Claude output. They lie in bed and lose sleep over the jobs they can start before they black out. One question runs the show. What can I run while I am out?
A novel feels indulgent.
A movie with no laptop open feels wasteful.
One voice in your head says that something could run right now.
The voice never shuts off.
That is Token Anxiety. The frightening part is that the anxiety is rational. That is exactly why it sticks.
The Rational Trap
Every week a new benchmark makes last month's workflow look prehistoric. A new model ships overnight. Context windows double. Opus gets faster. Sonnet gets cheaper.
None of this reduces the pressure. It multiplies the pressure.
You can do more now, and somebody already does. The window to build first, or to ship first, shrinks by the day. That is a literal claim and not a figure of speech.
Tech circles once felt like a raw electric field of opportunity. The message ran "there is so much to build, come try things." Excitement ran high. The optimism was genuine, infectious and reckless.
Look at the same circles now. The energy inverted. The message no longer says "come build exciting things." It says "I better keep working, because one hour of rest costs me everything." The tone moved from opportunity to desperation. It moved from "I get to build" to "I must build or I drown."
That is a different problem, and it eats people alive.
The Faustian Bargain of Vibe Coding
I will be honest with you. I forced myself into the vibe coding world. I build things with agents and I start projects through conversational prompts. I want to understand the hype.
Here is what actually happens.
The beginning seduces you. The idea is simple. You describe it in a few words. The rough scaffold comes up fast. You get a minimum viable product, or MVP, in hours. The speed feels electric.
Then the fixes start. Each fix needs more prompting, more waiting and more context-loading. The cycle runs brutally long, longer than a Rust compile cycle. Each fix also spawns two more tweaks you want, and those spawn two more. The work grows exponentially.
Here is the insidious part. Each new project starts so easily that you soon run four or five of them at once. Every one of them sits in its crappiest version. Every one of them demands your attention. You babysit small steps and type explanations in English to fix work that takes 10 keystrokes in real code.
You build more than you ever built in your life, and you accomplish less than ever.
You write 10,000 lines of code in a day with no effort. Those 10,000 lines are not good. You feel no satisfaction. You did not even build the right thing.
The Selection Problem
Nobody talks about this part.
Before AI you could not try every idea. You had to select. You picked one problem, committed to it and pushed through it. That constraint was a gift. It forced you to prioritize. It forced you to solve the right problem, because you could not afford to solve the wrong one.
Now you run three or four ideas at the same time. Every one of them stays half-baked. Every one of them grows in scope at an exponential rate. The work multiplies, the task juggling spirals, and the productivity metrics climb.
And nothing ships.
People spend $1,000 a day on API tokens. They build constantly. They jump from project to project. They run agents 24/7.
And they have literally nothing to show for it.
The programming was never the bottleneck. The bottleneck was always the choice of what to build. AI removed the wrong constraint. It made execution trivially cheap, and it did nothing about the hard problem. The hard problem is the decision about what matters.
The Split-Brain Problem
A fracture opens inside every developer who straddles the old world and the new one. You hand-code something, and halfway through a function one thought creeps in. "I could vibe code this in 30 seconds." So you start an agent. Now you stand in two worlds at once, with one foot on the platform and one foot on the train.
You feel the pull of the agents all day. "Better start a quick one." "Let me prompt this side feature." That buzzing sensation grows and compounds. It is anxious energy in the mask of productivity. It is the energy of a person who knows that work could happen and does not happen.
What This Actually Costs
Let me be direct.
I lived in that state before, long before AI arrived. I pursued building without a stop. I stayed up through entire nights to program. I felt anxious at social gatherings, because part of my brain wanted the editor back. Every minute away from code felt like a wasted minute.
It damaged friendships. It turned me into a process instead of a person.
AI agents bring that exact feeling back. The feeling runs louder now, because the machine never sleeps. The machine is always ready. There is always another prompt to send. There is always another project to start. The guilt of rest is infinite, because the capacity for work is infinite.
That is not productivity. That is an addiction in a hoodie.
The Advice I'd Give Myself
One extra feature in your calendar app does not pay for a good evening with your friends.
One more overnight agent run does not pay for the fog you carry into tomorrow's conversation with someone who matters.
The 10,001st line of code today will not change your life. The moment you miss tonight might change it.
Hard work is a vehicle. It carried you here. It is not who you are. Confuse the vehicle with the identity, and you stop being a person and start being a process.
A process does not have dinner with friends. A process does not read novels. A process does not watch a movie with full attention and feel something.
You are not a process.
The machines run without you, so let them run. Turn off the terminal. Close the laptop. Leave the agents unsupervised for one evening.
The code stays there in the morning. The same bugs stay, the same half-baked MVPs stay, and the same growing task lists stay.
The people around you will not always stay.
Token anxiety is real and the pressure is real. The thing you race against is only a feeling. You have no competitor here. A feeling does not ship a product.
Ship less. Ship meaningful work. Choose better. Live more.
Related reading: AI Costs Part 1, Claude Code Memory Architecture
