创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

AI编程成本应按交付成果衡量

AI 总结

MIT Technology Review AI刊载的HPE赞助内容称,AI编程智能体消耗的token可能是普通聊天提示的10至50倍,因此仅统计token或统一限额难以反映开发价值。文章建议以每个已合并拉取请求的全口径成本衡量投入,并同时跟踪返工和缺陷;HPE称其将150多个内部应用的例行工作路由至本地开放权重模型,使token成本下降30%至50%。

深度见解

这为AI辅助开发提供了可执行的单位经济指标,但基础设施效果及相关案例来自HPE赞助内容,仍需独立验证。

When a developer gives an AI agent a coding task, the agent does more than answer once. It plans, generates code, runs tests, and repeats the process to correct errors. A single task can use 10 to 50 times more tokens than a basic chat prompt. The more useful the agent becomes, the more calls it makes. With per-token pricing, the workflows creating the most value can also become the most expensive.

The financial pressure is already visible. Uber reportedly exhausted its entire 2026 AI budget by April after expanding its use of Claude Code. GitHub Copilot moved from flat-rate pricing to metered credits. Gartner predicts that AI coding token costs will surpass average developer salaries by 2028.

The natural response is rationing usage caps, seat limits, and approvals before developers launch agents. But blanket limits can restrict the workflows delivering value. They also optimize the wrong number. Cost per token measures consumption, not results. Some spending reflects waste, including retries and runaway loops. Some represents the work of shipping software. A meter cannot distinguish them, and neither can a spending cap.

#HPE#HPE Private Cloud AI#Claude Code#GitHub Copilot#Uber#Gartner

原文约 4 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。