There's a guy at every tech meetup now. You've seen him. Laptop half-open, walking through the venue like he's carrying a newborn. If you ask what he's doing, he'll tell you. Eagerly.
"I'm running an agent. It's been going for four hours."
On what? Doesn't matter. The point is that it's running. The point is the tokens.
The Leaderboard
Somehow, in the last year, token consumption became a status symbol.
There are actual leaderboards. People posting screenshots of their usage dashboards like they're Strava runs. "Hit 47 million tokens this week." Reply guys falling over themselves. "Beast mode." "Absolute unit." Someone asks what they built. No reply.
The philosophy, if you can call it that, goes something like: "Tokens are thought. I'm conducting more thought than anyone else."
Let that sink in for a second. Tokens are thought. Not your thought. Not directed thought. Not thought aimed at solving a specific problem for a specific person. Just... thought. Volume of thought. As if intelligence is a commodity you purchase by the million and spray at your screen until something happens.
These are the same people who will mass-reply to any thread about AI capability limits with "you're just not using enough context" or "try giving it more runway." As if the problem with every failed AI project is that it didn't consume enough tokens. As if the right amount of money fixes the wrong amount of thinking.
The Cap Complainers
Then there's the adjacent species: the cap complainers.
Every time a provider adjusts usage limits, these people erupt. Furious. Betrayed. They were burning through hundreds of dollars a month and now the ceiling moved and they're hitting it. The posts read like someone cancelled their gym membership mid-set.
I've been using AI tools professionally for over a year. I rebuilt an entire enterprise application in a month. I've built a dozen personal tools I use every day. I built a karaoke production platform, an AI health system, and an agent orchestration framework that maintains five repositories.
I have never hit my cap. Not once.
And I'm not being cute about that. I'm not bragging about efficiency as if it's a personality trait. I'm asking a sincere question to the people burning through limits that are frankly enormous:
What are you building?
Where is it? Can I use it? Can anyone? You're spending $300, $500, $800 a month on tokens and posting about it publicly. You're literally keeping score. So where's the scoreboard that matters — the thing you shipped?
The Math Doesn't Math
Here's what I think is actually happening.
Most of the heavy token consumers aren't building. They're churning. They're starting projects, hitting a wall, starting over with a new prompt, hitting another wall, and asking the model to "try a different approach" fourteen times in a row. Every restart burns tokens. Every vague prompt burns tokens. Every "fix it" without context burns tokens.
That's not AI-assisted engineering. That's a very expensive slot machine.
When I sit down with an agent, I know what I want built before I open the terminal. I've thought through the data model. I know where the feature lives in the system. I know what "done" looks like. The agent gets clear, specific direction, and it executes. If it gets something wrong, I know why it's wrong and I can explain the correction in one shot.
That's why I don't hit the cap. Not because I'm using AI less. Because I'm using it well.
The token bros are using it the way a kid uses a firehose — maximum pressure, zero aim, soaking everything including themselves. And then complaining that the water bill is too high.
The Laptop Thing
I keep coming back to the half-open laptop. Because it's such a perfect metaphor for the whole thing.
The laptop is half-open so the agent keeps running. You're at lunch. You're at a meetup. You're walking between conference sessions. Your laptop is half-open because you need the world to know that something is happening inside it.
But what's actually happening? An agent is spinning. On what? Toward what? With what review process? Under whose architectural guidance?
Nobody walks through a conference with a half-open laptop running a compiler. You don't see people cradling their machines because their test suite is executing. Those are means to an end, and nobody cares about the means.
Tokens became the end. The consumption is the product. "I used more than you" is the flex, not "I built something you can't."
The Culture Underneath
This is what happens when a tool becomes an identity.
It happened with crypto. It happened with NFTs. It happened with every wave that's ever hit tech. The tool itself has real value — I believe that more than most people, because I've staked my career on it. But the culture that forms around the tool is almost always unhinged.
The token bros aren't engineers who use AI. They're AI enthusiasts who pretend to engineer. The distinction matters. An engineer starts with a problem and reaches for whatever solves it. An enthusiast starts with the tool and goes looking for a problem to justify it.
When the tool is the identity, you optimize for tool usage, not outcomes. You brag about consumption, not creation. You build leaderboards around input, not output.
And you walk around a conference with your laptop half-open, hoping someone asks what you're running, so you can tell them how many tokens it's burning.
Nobody asks what it's building because you don't have an answer.
The Actual Point
AI tools are the most significant force multiplier I've encountered in 17 years of engineering. They are genuinely, profoundly useful. I have built more software in the last year than in any five-year stretch of my career, and I've built it better.
But the force is multiplied against what you bring to the table. That's what the course bros don't understand, and it's what the token bros don't understand either. If what you bring is clear thinking, strong architecture, and specific intent — a modest number of tokens goes a very long way. If what you bring is vibes and a credit card, you can burn through a million tokens and have nothing to show for it except a screenshot of a dashboard.
Tokens aren't thought. Tokens are a resource consumed during thought. The thought is yours. If you don't have any, no amount of tokens will compensate.
So the next time someone tells you they burned 50 million tokens this week, ask them the only question that matters:
What did you ship?