There's a ritual forming in the Claude Code world. You can watch it happen in the tweets or Reddit posts every week: a few hours before the weekly usage limit resets, people look at their remaining allowance, feel a little twinge, and start feeding the machine. Giant refactors nobody asked for. Speculative features. "Rewrite my whole test suite" at 11pm. Not because the work needed doing, but because the meter was about to reset and letting the leftover usage expire felt like pouring money down the drain.
I get it. I've felt the twinge. But let's take the ritual apart, because the feeling driving it is one of the oldest bugs in human wiring, the logic underneath it doesn't survive contact with arithmetic.
Why the twinge happens
This is loss aversion for developers or vibe coders. Losing something feels roughly twice as bad as gaining the same thing feels good, and an expiring allowance is engineered, accidentally, to trigger exactly that circuit. The unused tokens read as a loss. Never mind that you can't bank them, can't sell them, and didn't have a plan for them, at 11pm on reset eve they transform into something being taken from you, and the brain says you should do something.
It's the eating at a buffet problem. Nobody needs the fourth plate at the buffet. You eat it because you paid the entry price and your stomach has now become an accounting department. The plan works the same way: the $100 or $200 went out on day one, and every unused drop of allowance starts to feel like the buffet restaurant winning. So people burn the remainder to feel like they won. What they actually got is the token equivalent of being uncomfortably full: a repo of generated stuff they'll never read.
The math the ritual skips
Here's the part the twinge doesn't want you to think about. You didn't buy tokens. You bought access, and we went deep on this in the piece on whether Anthropic actually loses money on Max plans: the subscription's value is the option to use frontier models whenever you need them, at a price you were willing to pay. An option you didn't fully exercise this week wasn't wasted, any more than your insurance was wasted because your house didn't burn down. So what I'm saying is the allowance is a ceiling, not a target.
Meanwhile the burn itself has real costs, just not where you're looking. It costs your evening, “TIME” is the one genuinely non-renewable resource in this whole hobby. And it produces liabilities dressed as assets: every speculative refactor and unrequested feature is code you now own, unreviewed, unrelated to your actual goals, sitting in your project like a junk drawer you pay rent on. Burning usage to generate work you didn't need is not getting your money's worth. It's doing chores for the loss-aversion circuit.
The collective version is worse
Zoom out and the ritual gets funnier, in a bleak way. Capacity is the scarcest thing in AI right now. It's the stated reason limits exist, the reason they get tuned, and the reason expensive models keep getting harder to reach, a squeeze we covered when we asked how long these tools stay cheap. Every reset eve, a crowd of subscribers simultaneously floods the datacenters with make-work to avoid "wasting" allowances, which drives up exactly the demand curves that get allowances tightened. The ritual to protect your usage is a tiny vote for everyone getting less of it. Nobody intends that. Tragedies of the commons never feel like votes from the inside.
Keep the ritual, change the fuel
I don't actually think you should kill the habit, because the habit contains something good. A recurring block of hours where you feel license to run the expensive model freely is actually valuable. The problem was never the burning, it was burning it on junk invented in the moment. So aim it towards the right things instead.
Keep a boring-backlog file. Every time you skip something during the week because it's not urgent, write it down: the test coverage you keep promising yourself, the documentation drift, the dead code, the accessibility pass, the dependency updates, the CLAUDE.md tune-up, the security once-over you've been meaning to run since you read the post about shipping without looking. None of it is fun. All of it is real. Then when reset eve comes and the twinge hits, open the file and let the machine eat its way down the list. Same psychological payoff, same busy terminal, except Monday morning you wake up to a healthier codebase instead of a junk drawer.
Use it or lose it was always the wrong frame. You never lose the tokens, they were never yours to keep. The only thing on the table every reset eve is your evening and your codebase, and the ritual can either spend those or invest them. Burn the allowance if it makes you happy. Just burn it on the boring stuff, and let the accounting department in your stomach finally take a night off.
