Five things from Friday's eleven that stuck with us: - An Amazon team estimated a new inference dat...
TL;DR · AI 摘要
本文揭示了多个科技公司在AI应用和工程实践中的挑战与创新，包括亚马逊团队效率提升、Uber代码审查时间延长及AI工具的使用问题。
核心要点
- 亚马逊6人团队76天完成原计划30人18个月的项目
- Uber代码审查耗时从2024年3小时增至2026年9小时
- Figma工程师因AI分析质量被质疑而手动审核所有PR描述
结构提纲
按章节快速跳转。
思维导图
用一张图看清主题之间的关系。
查看大纲文本（无障碍 / 无 JS 友好）
- AI工程实践挑战
- 亚马逊案例
- 团队效率提升方法
- Uber实践
- 代码审查耗时增长
- uReview工具应用
- Figma AI问题
- AI分析信任危机
金句 / Highlights
值得收藏与分享的关键句。
亚马逊6人团队76天完成原计划30人18个月的项目，效率提升显著。
Uber代码审查耗时从2024年3小时增至2026年9小时，uReview工具每周生成25,000条评论。
Figma工程师因收到低质量AI分析而手动审核所有PR描述，凸显AI工具可靠性问题。
AI Engineer on X: "Five things from Friday's eleven that stuck with us: - An Amazon team estimated a new inference data plane at 30 people and 18 months. Six engineers, two of them Distinguished, built it in 76 days. Productivity went down first in almost every team studied - At Uber a first code" / X
AI Engineer
@aiDotEngineer
Five things from Friday's eleven that stuck with us: - An Amazon team estimated a new inference data plane at 30 people and 18 months. Six engineers, two of them Distinguished, built it in 76 days. Productivity went down first in almost every team studied - At Uber a first code review took three hours in 2024. Nine in 2026. uReview now leaves 25,000 comments a week, and the model is 100% sure every time, including when it is wrong - Over 70% of Uber's PRs come from agents. The maintenance loop runs on Sunday, when CI has capacity and nobody wants a Monday of extra diffs - A Figma engineer sent a respected skeptic an unlabeled AI analysis. Reply: I did not expect someone I respect this much to send me something this sloppy. Now every PR description opens by hand - The same prompt takes two seconds or sixty. A reasoning model's normal is a chat model's outage. That is why you keep seeing "something went wrong, please try again" Watch the AI-Native Enterprises playlist. Part 2 lands tomorrow:
youtube.com/watch?v=ZIYYsA…
10:50 PM · Aug 28, 2026
1K
Views
2
1
4