Amazon warns engineers just using more AI doesn't make them more productive, says they should avoid tokenmaxxing

"Deeply flawed" metrics such as AI token usage aren't always a good measure of success, Amazon tells engineers.

Amazon tells engineers to focus on real results, and urges developers not to blindly focus on AI tool usage. The era of the "Renaissance Developer" using all kinds of AI is here.

It also urges workers to shun tokenmaxxing, and focus on building a deeper connection with customers.

Amazon has told its engineers to look beyond simply using AI to ensure their work gets done, and focus instead on the results of their labor. In a memo sent to its workforce, the company warned against using "deeply flawed" metrics such as AI token usage or code generation as a measure of team success.

It also cautioned against workers chasing "tokenmaxxing", noting how, "our most prolific engineers have demonstrated that neither the developer role nor their output is defined by the use of AI."

The age of the "Renaissance Developer"

The memo, written by Terk Terkowitz, Amazon VP/Distinguished Engineer, Worldwide, and entitled "An update from Amazon engineering leadership on the role of the developer in the age of AI", signaled the apparent beginning of a new era in how the company defines its workers in the age of AI.

This includes the age of the "Renaissance Developer", who is able to blend AI tools with human judgment and domain expertise "to build entirely new things".

"AI is changing the work of software engineering both more quickly and more fundamentally than these previous trends," Terkowitz noted. "What it means to be a software engineer, and what software engineering even is, is changing quickly and durably."

What this means for Amazon's workers is a focus on "on what is not changing as we evolved the SDE (Software Development Engineers) roles".

Sign up to the TechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!

This will mean a move away from "deeply flawed" metrics such as token usage or adoption of AI tools, and more focus on the impact on customers, businesses and teams.

The memo urges managers and division heads to make sure that there is "sufficient understanding" among their teams about the benefits AI tools can bring, and told workers to ensure they become "deeply connected" to their customers in order to gain a deeper knowledge of what they really need from Amazon.

"Despite the speed of change, we believe that it is still early. We all need to embrace this change and take the time to learn, or we risk being left behind," Terkowitz concluded.

"We're just seeing the beginning of AI's effect on software engineering. While we have a vision for what the future looks like, there's a lot that's still emerging. We are certain that whatever future best practices are, AI will be at the center of software engineering practice."

Follow TechRadar on Google News and add us as a preferred source to get our expert news, reviews, and opinion in your feeds.

Mike Moore is Deputy Editor at TechRadar Pro. He has worked as a B2B and B2C tech journalist for over a decade, including at one of the UK's leading national newspapers and fellow Future title ITProPortal. When he's not keeping track of all the latest enterprise and workplace trends, he can most likely be found watching, following or taking part in some kind of sport.

You must confirm your public display name before commenting. Please logout and then login again, you will then be prompted to enter your display name.