Amazon’s Terkowitz urges engineers to document AI tooling gaps
Terk Terkowitz, a leader in Amazon’s engineering team, wrote in an internal update that if AI tools don’t help an engineer’s work, that’s a valid finding—not a shortcoming. He urged developers to explain where AI falls short, share those insights with peers, and push for solutions. The message frames AI adoption as a process of continuous assessment rather than an all-or-nothing requirement.
Key points
- Terk Terkowitz told Amazon engineers AI tooling gaps are valid findings, not failures
- Developers should document where AI doesn’t help and share findings with peers
- No specific tools or tasks mentioned; update is internal and unconfirmed publicly
Terkowitz’s note does not specify which AI tools Amazon engineers use or which tasks remain unaddressed. It aligns with broader industry discussions about AI’s uneven impact across roles, emphasizing transparency and iterative improvement over rigid expectations. The update was shared internally but not publicly confirmed by Amazon.
The story so far
2 episodes →- Amazon’s Terkowitz urges engineers to document AI tooling gapsthis story
Quoting Terk Terkowitz
Simon Willison · 28 October 2026Loading the full article…
This text was published by Simon Willison and written by Simon Willison. It is reproduced here with attribution so you can read it in full; the rights remain with the publisher. Read it at the source ↗
The headline, key points and digest above were generated by Digest AI's editorial model from the linked sources. Automated summaries can contain errors: the sources are the record. Spotted a mistake? Tell us. Published by Martin K., who runs Digest AI and handles corrections.
More in Society & Work
All →- Climate activists urge funding shift from AI to grassroots resistance · 1 src
- xAI offers Mississippi residents buyouts to avoid noise lawsuit · 1 src
- Jeanette Winterson argues AI future depends on human choices, not technology · 1 src
- Survival LLM offers offline AI assistant with emergency guides · 1 src
- VisionQuest: AI goes rogue, sparks debate · 1 src
Comments
via GitHub Discussions