Skip to content

AI Coding Cost Proposal Focuses on Merged Pull Requests as HPE Reports Savings From Model Routing

1 reports 1 reporting sources Updated 3 hours ago

Understand the event

AI overview

An MIT Technology Review article recommends measuring AI coding costs per merged pull request rather than relying on token counts or usage caps, and reports that HPE has reduced token costs by 30 to 50% through a hybrid model platform. The proposed measure divides total AI-assisted development costs by the number of changes that pass review and are merged, with rework and defects tracked alongside it. The article describes routing routine coding tasks to open-weight models and reserving frontier models for harder work. At HPE, the platform routes workloads from more than 150 internal applications to on-premises open-weight models; the reported savings apply to token costs.

Generated by AI from reports · Updated 1 hours ago

Read next

More changes in today’s briefingTypeSafe AI and Treg release open-source people search tool powered by Jev

Report timeline

Follow the reports to explore different sides of the event.

11/2
  1. Stop Counting Tokens: Measure AI Coding Cost by Merged Pull Requests

    The article argues that companies should measure AI coding costs by the cost per merged pull request, alongside rework and defects, instead of relying on token counts or usage caps. It describes routing routine coding tasks to open-weight models and reserving frontier models for harder work. At HPE, a hybrid platform routes workloads from more than 150 internal applications to on-premises open-weight models, with reported token cost reductions of 30 to 50%.

Keep up with AI, one email a day

Model releases, price changes and compute developments, with original sources. Free, confirmed by email, and easy to unsubscribe. Read a past issue

Event heat trend

There is not enough continuous observation data to plot a trend yet.