Maximize value, not token usage, Amazon has told its engineers, citing concerns about rising AI costs and complexity. Amazon made the strategy shift public on Tuesday in a note to engineering teams outlining the changing role of its software development engineers in the age of AI. “Our most prolific engineers have demonstrated that neither the developer role nor their output is defined by the use of AI,” Amazon VP and distinguished engineer Terk Terkowitz wrote in the note. “We’re now in the era of the Renaissance Developer, blending AI tools with human judgment and domain expertise to build entirely new things.” In other words, Amazon wants its developers using AI, but burning through tokens isn’t the same thing as getting useful work done. Rather than define the developer role by how AI is used, the memo focuses on what isn’t changing so fast: the need to deliver useful software and results for customers and the business. “It is difficult to define, in a way that will stand the test of time, what good AI powered engineering practices look like,” the memo continues. “We have decided to focus on what is not changing as we evolved the SDE roles … the outcomes that matter aren’t changing, even if the inputs, tools, and techniques are changing faster than ever.” What that means for software developers in the present moment is that AI input metrics, even if Amazon has seen some correlation with increased productivity and delivery on tokenmaxxing teams, aren’t what Amazon sees as a measurement of good use of developer time and resources. “We are all aware of how deeply flawed these metrics are, primarily because they are disconnected from what matters,” the memo argues. “[U]sing these metrics could, if used as a target instead of a measure, drive negative outcomes, increasing costs, and increasing complexity,” the memo continues, referring to tokenmaxxing costs and overly complex code that’s at odds with Amazon’s mission to “invent and simplify.”…
