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? 0 comments on Hacker News.
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?
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? 0 comments on Hacker News.
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?
Hacker News story: Ask HN: Corporate Disconnect Between "Tokenmaxxing" and Token Optimization
![Hacker News story: Ask HN: Corporate Disconnect Between "Tokenmaxxing" and Token Optimization]()
Reviewed by Tha Kur
on
May 31, 2026
Rating:
No comments: