Tokenmaxxing is dead, long live tokenmaxxing

theahura 132 points 159 comments June 28, 2026
12gramsofcarbon.com · View on Hacker News

Discussion Highlights (20 comments)

aurareturn

Tokenmaxxing was just a way to force employees to start leveraging AI in a meaningful way. For companies that have measured performance based on token spend, they can now dial it back. Employees have learned to leverage AI for things they wouldn’t have prior. Now they know what’s possible and what’s not. No one is stupid enough to always measure performance based on token spend and have unlimited budget. It was always a temporary thing to transition the employees to a new world. Management felt like employees weren't leveraging AI fast enough. That's why in 2025, there were many mainstream articles about how CEOs were forcing their employees to use AI or get fired. Tokenmaxxing was just the other extreme. Companies will arrive at an equilibrium. There's no need to overthink this. Edit: One reply cited this X post as an example of why management needed to do this. Trying to change a company with hundreds/thousands/tens of thousands of employees is hard. You have to send one simple message at a time. https://x.com/danluu/status/1487228574608211969?lang=en

linsomniac

>I’ve basically never heard a business leader say that they were going to set a bunch of money on fire because it made them feel good. Really? ~4 years ago our CEO hired a consultant to fly out several times to do team building exercises. We can't afford to do our 3-year server refresh cycle, but the consultant was no problem to pay. We just recently had branding consultants come in and also spent thousands of dollars (AWS charges) on rebranding all our photos. We operate in a captive market, if you want to operate in our market you are required to subscribe to our service, and if you aren't in our market you can't subscribe. Branding at the end of the day drives 0 sales. Heck, reminds me of the time a company I was working with hired a new CTO and one of the first things he did was as "server renaming scheme" using obscure (to the US-centric staff) city names from around the world (database servers are Swiss city names, web servers are Denmark, storage is Finland). We went from cattle naming to pet naming, for a CTO that lasted ~6 months. In my experience company leadership is not quite as thrifty as this article likes to think they are.

baconmania

The implication that tokenmaxxing was an intentional and thoughtfully considered approach rather than blind hype-following by an overpaid manager class who are too far removed from value to understand the downsides of LLMs is hysterical beyond belief.

behnamoh

Tokenmaxxing was never a thing to begin with. Just because a few companies did it doesn't mean it was a widespread phenomenon.

j45

Beyond getting momentum going for a cmpany, Tokenmaxxing is lighting money on fire. The idea of tokenmaxxing reaches different companies in different waves, so it will be discovered in waves and outgrown in waves in companies and industries in their own cycle. In the long run, tokenmaxxing is like drunken sailor spending. Scaling is almost always about a large component of efficiency, and lighting money on fire in the street can only last so long.

fraywing

Brute forcing positive outcomes by spending more tokens until a happy path manifests does not solve the underlying comprehension (and liability) problem. I fear a world where critical software is stood up with increasingly non-human governed abstraction because it [seems like it] works . Software engineers as the review terminal in a conveyor of business-led code mass production... coming to a company near you?

gausswho

It's AI usage mandates now, but rather than focusing on how the current hot topic has ripped through the business world, often without benefit nor repercussions at leadership, I'd prefer to analyze the higher pattern. We've recently experienced such ripples as the metaverse, blockchain/nft/web3, 'the cloud' (and a minor wave of cloud gaming). There was even a teacup buzz of 'apis', oddly disconnected from the semantic web. Why do such fever dreams occur at all? Are they getting more prevalent? More damaging? Do they jepaordize the global economy? Should they be regulated in some fashion? I can't prove my case, but I think it's a symptom of media manipulation/consolidation, the 'fiduciary duty' delusion, and that shareholders can hold the puppet strings tighter than they used to. More and more, they place their sillytown bets and expect the plebs to dance to them.

theanonymousone

What is meant by a "loop" here? Just repeating the same prompt until you get the desired result? Are subsequent repetitions too close to each other?

impish9208

“Thing is dead, long live thing” is dead, long live “thing is dead, long live thing.”

jtrn

Better title more in line with the content of the article would have been: The reports of tokenmaxxing’s death are greatly exaggerated. Pet peeve of mine is nonsensical usage of the x is dead, long live x.

IceHegel

Funny, now it's the management saying "Go be a bohemian, experiment, spend freely." and the employee saying, "Hold on, where's my ROI?"

kaizenite

This seems to happen with most big tech adoption in the first few years. The big data boom in the early 2010's had execs just buying up spark clusters and data lakes before they even had a clear analytical use case or governance.

mvkel

At least it's being used. There are many examples of tech over-adoption, like building out capacity for 1M concurrent users, only to see 50.

EGreg

I don’t think people who write these headlines understand that “long live the king” used to refer to the next king. Where is the next tokenmaxxing?

et1337

Folks have been saying “things are different now, the agents are now compounding success instead of error” for at least a year now, but I just don’t see it. I was lucky enough to receive a weeklong $50k per head AI training from the people saying these things, and one of their few helpful concrete recommendations was to constantly clear context all the time, to avoid things going off the rails. However, I think finding security vulnerabilities is one use case where it doesn’t matter. Tokenmaxxing is absolutely effective for that. We as an industry are in the middle of adopting very expensive, complex continuous fuzzers.

red_admiral

> Like, imagine if some serious business leader, like, idk, Mark Zuckerberg, decided to announce that Meta was going to burn money. Like ... pivoting to the "metaverse" and changing the company name to show he's serious.

dofm

This is like hell, if hell was being stuck on a really poorly-maintained uncomfortable rollercoaster forever.

natyoung

Studies have proved that you'd have been better off with fartmaxxing.

ambicapter

> That’s no longer true. We’ve entered a different regime, where spending more tokens generally results in better results. We call this “compounding correctness” — the more tokens you spend on getting a task correct, the more likely you’ll get a good outcome. We talked about this a bit at the last in person Agentics meetup: Have we? Is it generally the case that the more tokens you spend, you better results you get? This take is so weird I suspect author somehow financially benefits from tokenmaxxing.

chaboud

This is more likely the junior camper version of "not everything that counts can be counted, and not everything that can be counted counts." In the early days of LLMs, we saw the classic hype-driven bi-modality of opinions. Folks were in the "fake news, fad" camp, or they were in the "omg, take over the world" camp. Those of us closer to the space, with the awareness to know that there was some truth (and a lot of misjudgment) to go around, were in the middle of nowhere. When I co-wrote some driver code with Chat GPT, other engineers (and even one of our directors) told me to keep it quiet. At the same time I had directors and VPs asking me how we could accelerate adoption. For a while, I had access to a cheat code just because I had the audacity to not ask for permission. Folks were sure I would get in trouble for spending thousands per month in LLM operation, but a handful came along for the ride, burning tokens like firewood and learning along the way. Tokenmaxxing is probably coming from at least a few things: 1. A course-correction for the practiced frugality that kept folks from jumping in and just learning at the ragged edge. 2. A willful and deliberate recognition that the best innovations in the later phases of a disruptive introduction often come from sparks of ideation in concentrations of activity. In other words, we don't know where good is, and we need to find it. (Charitable interpretation from the article) 3. Recognition that, even if they don't know why, leaders and product owners will get punished for not jumping in and, because of bullets 1 and 2, won't get punished for trying and missing. Even if they have no idea what they're doing, they're going to fake it until they make it (or slide into another job). This last set is where the pain lives. An organization with healthy and increasing AI tool usage will see elevated token counts, but so too will one using LLMs to rewrite wikipedia articles without the letter "m" to keep token counts high. These are pathological behaviors brought on by conflated metrics. We had discussions about this in the early LLM days, where my old team was looking to ship new capabilities for older products. There was a lengthy VP-level discussion about getting to "80% usage" of the new system vs the old. Because the new system was a superset of the old, I eventually said "we can do that immediately, but it's a cost goal, where we're just aiming to make our business more expensive to operate, rather than a value goal for our users". We didn't adopt the target, but folks were understandably frustrated that they didn't have a straightforward way to measure and report progress. Tokenmaxxing is, inevitably, a conflated goal, but it's what we have right now. Take advantage of the moment, learn, build, and keep an eye on levers for efficiency.

Semantic search powered by Rivestack pgvector
14,015 stories · 131,331 chunks indexed