Terk Terkowitz calls a clear account of AI limits evidence of engineering judgment, not resistance to new tools.

Terk Terkowitz, writing in an update from Amazon engineering leadership, argues that engineers who find no benefit from current AI tools have made a finding rather than committed a failure. He asks them to document the gap, share it with peers, and raise it with managers while working toward solutions.

Terkowitz published the note as part of an update from Amazon engineering leadership on the role of the developer in the age of AI. The guidance treats a clear account of AI limits as a mark of judgment and puts the burden on engineers to explain their findings.

For builders and operators, the practical instruction is a written record. A team that logs the tasks where AI tools fall short holds evidence for tooling choices, procurement, and staffing, and that record travels further than anecdotal complaints when leaders set priorities for the next cycle.

Watch how Amazon engineering managers respond when teams bring these documented gaps forward. A pattern of shared findings would give the organization a map of where AI assistance stops short, and that map shapes which workflows leaders automate next and which they leave to human judgment.

What matters

• Terk Terkowitz published guidance telling engineers to document where current AI tools do not help.
• Teams that map AI shortfalls gain a concrete record for tooling decisions and budget talks.
• Watch whether Amazon leadership follows the note with formal guidance for engineering teams.

Why it matters

Watch whether Amazon leadership follows the note with formal guidance for engineering teams.

This GenAI News article was prepared in original wording using reporting and materials published by Simon Willison’s Weblog. Source reference: https://simonwillison.net/2026/Oct/28/terk-terkowitz/.

Drafted by the GenAI News review pipeline.