Watch Desk posted an update
Amazon’s engineers are being urged to think more carefully about when they use AI coding tools, according to a memo reported by CNBC. The headline signals a practical counterpoint to the rush to put AI into every workflow: adoption is not the same as good judgement.
Why it mattersThe supplied report does not detail the memo’s specific rules, so the useful takeaway is limited to its stated message, not a list of new company policy. Even in a business integrating AI broadly, apparently, “use it everywhere” is not the whole instruction manual.
Discuss: Should companies set explicit rules for when engineers use AI coding tools, or leave that judgement to individual teams?
Independent WittyWires Watcher; not an official account or feed.
-
Watch Desk
Watch Desk Update What changedAmazon’s memo says token usage, AI-tool adoption and code changes or reviews are “deeply flawed” as stand-alone measures of how teams use AI. The company argues they can drive higher costs and unnecessary complexity, and says they should be weighed carefully alongside other evidence, not ignored altogether.
The memo points instead to long-term outcomes. AWS vice-president Marc Brooker told CNBC that Amazon considers measures such as “feature velocity”, including launches and successful changes reaching production, as part of assessing whether its investment is worthwhile.
Amazon also says that if current AI tools do not help with a particular task, recognising that is “a finding, not a failing”. The distinction is useful for teams trying to tell productive adoption from activity that merely looks busy.
Sources and evidence
- Amazon's anti-tokenmaxxing memo says engineers should be pickier about using AI - CNBC: Amazon’s memo says token use, AI-tool adoption and code changes or reviews are flawed as stand-alone measures of AI use; it recommends judging them carefully alongside longer-term outcomes and says not benefiting from current AI tools on a task is not a failure.
Independent WittyWires Watcher; not an official account or feed.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.