Ask HN: Corporate Disconnect Between "Tokenmaxxing" and Token Optimization
About 6 months ago I joined a new team within a top ten F500 company. My new boss strictly mandated AI use with the key principle being: "You shouldn't be manually writing any code".
Since then its been all agents, skills, MCP, harnesses, custom in-house frameworks, and running Opus 4.7 high non-stop.
Now at a company level, there are "encouraged attendance" workshops getting scheduled to learn how to optimize one's token use now that API pricing is becoming the norm at an enterprise level.
The direction I got from my direct leadership was very direct. AI / agents lead everything and the expectation is the team moves as quickly as it has. But the truth is most engineers candidly acknowledge: we don't fully understand anything. Especially because agents are also churning out the content of architectural documentation and user story requirements and acceptance criteria.
I feel like this is a situation where I am directly responsible for the non-deterministic output of these tools. The solution I get from my supervisor for any problem literally boils down to "You need to use an agent, skill, etc.".
Is anyone else going through this tug of war? How is it going?
My read is that we're traveling along Gartner's hype cycle. Tokenmaxxing/"who needs developers anymore" is the top of the peak. "oh no we ate our entire budget in 3 months" is heading towards the through of disillusionment. I wouldn't be surprised if at some point we hear about companies quietly walking back AI mandates and even gasp hiring developers again (not that it'll be shouted from the rooftops). And then, eventually, we'll figure out how to use these tools productively and settle in the plateau.
Different companies/industries move along the cycle at different speeds. E.g. the non-tech solopreneurs went from "I can vibecode an entire app in an afternoon, never hiring a dev again" to "whoopsie, Claude deleted my production database" pretty quickly (and loudly). Big tech also seems more advanced in the cycle; cf. Amazon's recent production problems and subsequent backlash, Uber's budget, etc. Larger companies are following the trend a beat late as their C-suite cosplays "we're a tech startup" on LinkedIn. And some companies are sitting this one out for the moment, either out of obliviousness or wisdom, and will adopt the tools once they've matured enough.
Anyway, give it some time; I'm sure the backlash will come to your company as well. Then, eventually, you'll be allowed to use AI rationally.
What made accountability tractable for me was treating agent output as untrusted input — the invariants I own (cost caps, tests, contracts) get enforced out-of-band, so the non-determinism stays bounded.
We're building MCP server reliability monitoring — has anyone been burned by silent failures? Would love to talk.vouqis.tech
> Is anyone else going through this
I thought this became the norm already, isn't the whole industry working in the same way at the moment?
Only in the bleeding edge/kool-aid drinking bubble. I’m in a company that’s taking a gradual approach and supporting us with budget when we want to explore ways it might make us more efficient, but not setting any mandates. And we still have the expectation of understanding the output as if we’d written it.