FOMO, JOMO, and FOWT — The Fear of Wasted Tokens

I wrote recently about token maxxing — deliberately spending more tokens on a problem because tokens are cheap and mistakes are expensive. Writing that piece made me notice something about my own behavior that I didn't like, and the more I sat with it the more I realized it deserved its own name.
This one isn't a tutorial. It's about a feeling. Three of them, actually — two you already know, and one that I'm fairly sure is brand new, because it can only exist in the exact world we just built.
FOMO — the one that got us all here
FOMO is the Fear Of Missing Out, and you don't need me to define it. It's the oldest emotion on the internet. In the AI space it has a very specific flavor right now: everyone else is shipping agents, everyone else is on the new model the day it drops, everyone else already rewrote their whole workflow around the thing that was announced this morning — and I'm still doing it the old way.
FOMO is a great motivator and a terrible advisor. It's the reason a lot of us learned this stuff early, and it's also the reason a lot of us have three abandoned side projects built on frameworks that were cool for six weeks. It pushes you toward action, but it's indifferent to whether the action was worth taking. Pure FOMO says: do the thing because everyone's doing the thing.
JOMO — the underrated counterweight
Then there's JOMO — the Joy Of Missing Out. It's the exact opposite feeling, and it's the one that takes actual maturity to reach.
JOMO is the quiet satisfaction of not chasing the new thing. Of watching a hype cycle go by and thinking, "I'll wait and see if this survives contact with reality." Of closing the tab. Of shipping the boring, working solution while everyone else rewrites theirs for the third time this quarter.
As a senior developer, JOMO is basically a professional skill. Half of experience is knowing which trains you're glad you didn't board. Not every new model, protocol, or framework deserves your weekend, and the peace that comes from knowing that is real. FOMO says do the thing; JOMO says the thing can wait, and some things you never need to do at all.
So far, so familiar. FOMO and JOMO are about how you relate to what's happening around you. The third feeling is different. It doesn't come from the outside world at all — it comes from my own invoice.
FOWT — the Fear Of Wasted Tokens
Here's my situation, and maybe it's yours too. I'm on the max plans — Codex and Claude Code — and on top of that I have a chunk of Azure tokens allotted every month. I pay a flat rate, and in exchange I get a big monthly ceiling of usage.
The catch nobody puts on the marketing page: these are monthly quotas, and they don't roll over. It's a use-it-or-lose-it bucket. Whatever I don't burn this month evaporates when the meter resets. I already paid for it. If I don't use it, that money is simply gone.
And that has done something genuinely strange to my head. I've caught myself:
- Feeling a pang of guilt for oversleeping, because those were hours the quota sat idle.
- Hesitating to take a day trip, doing the grim little math of "that's a whole day of tokens I'll never get back."
- Inventing work — spinning up runs I don't really need — just so the meter doesn't feel wasted.
That feeling needed a name, so I gave it one: FOWT — the Fear Of Wasted Tokens.
FOWT is not FOMO. FOMO is afraid the world is passing me by. FOWT is afraid my own prepaid quota is passing me by — draining away unused while I'm off living my actual life. It's a fear that lives entirely inside a billing cycle.
Why this is such a trap
If FOWT sounds familiar, it's because the psychology is ancient — we just pointed it at compute:
- It's the all-you-can-eat buffet, where you eat past full because you "paid for it."
- It's the gym membership you feel guilty about not using, even on the days your body needs rest.
- It's prepaid minutes burning a hole in your pocket at the end of the month.
In every one of those, the mistake is the same: treating a ceiling as a target. The quota is the most I'm allowed to use. Somewhere along the way my brain quietly rewrote it into the least I should use to "get my money's worth." Those are not the same number. They're not even close.
And here's the part that actually matters. I didn't buy the max plan so I could hit the max every single day. I bought it so that on the days I do go big — a gnarly migration, a full-fleet refactor, a real token-maxxing session — I never have to think about the meter. The quota is insurance, not a chore. Its value is that it's there when I need it, not that I drain it to zero every month like a tamagotchi that dies if I don't feed it.
The day I skip a trip to feed the meter, the plan has stopped working for me and I've started working for the plan.
Where the three feelings leave you
Lay them side by side:
- FOMO — anxiety that the world moves on without you. Pushes you to act, indifferent to whether it's worth it.
- JOMO — peace about letting the world move on. The earned confidence to sit things out.
- FOWT — anxiety that your prepaid quota resets unused. Turns a flat-rate ceiling into a guilt-powered daily target.
The cure for FOWT turns out to be the same muscle as JOMO, just aimed at your invoice instead of the hype cycle. Unused quota is not money wasted — it's slack you already paid for, exactly so that the busy days never pinch. Rest is not a leak in the budget. A day trip is not a rounding error against your Azure allotment. The plan did its job the moment it stopped making you think about tokens; if it's now making you think about tokens more, the anxiety is the bug, not the idle capacity.
So: use the quota when the work is real, and let it sit when it isn't. Oversleep. Take the trip. The meter resets on the first of the month either way — and no buffet was ever worth eating past full.