Amazon rejects tokenmaxxing in updated engineering guidance
Amazon updated its engineering guidelines to tell developers and managers to assess AI coding tools by the software teams deliver rather than by token consumption alone. The company warns against turning AI adoption, token usage, code changes or code reviews into standalone performance targets, recommending that managers compare high- and low-adoption teams and consider long-term outcomes. Amazon says usage data can still inform careful evaluation and maintains that AI will remain central to software engineering practice.
Amazon’s guidance provides a notable workplace framework for evaluating AI adoption based on delivery outcomes rather than inflated token consumption or internal usage metrics.
Amazon wants its engineers to quit chasing token counts, warning that heavy AI usage does not automatically mean better work. In updated engineering guidelines published on October 27, the company laid out how developers and managers should gauge AI’s real impact — and the takeaway is blunt: consuming more tokens is not the same as delivering more value. Amazon is not backing away from the technology, though. “We are certain that whatever future best practices are, AI will be at the center of software engineering practice,” the company wrote.
Go deeper with TH Premium: AI and data centers

- The data center cooling state of play
- The custom AI ASIC state of play
- America’s AI chip rules keep changing — and the rest of the world is paying the price
- GTC 2026: Ian Buck press Q&A transcript — VP of Hyperscale and HPC speaks out on shelving CPX and shipping LPU decode this year
- Demand for data center CPUs has surged, and AI agents are responsible