Uber Burned Its Entire 2026 Claude Code Budget by April. The COO Says He Can't Justify the Spend.

Uber's COO Andrew Macdonald told Business Insider what a lot of engineering leaders are thinking but won't say publicly: "Getting harder to justify money spent on tokenmaxxing." The backstory: Uber's CTO revealed the company burned through its entire 2026 Claude Code budget by April. 95% of Uber engineers use AI tools monthly. 70% of committed code comes from AI systems. And Macdonald still can't point to proportional gains in consumer features.

The 230-point, 300-comment Hacker News thread tells you this hit a nerve.

Here's what I think is actually going on. It's not that AI coding tools don't work. They clearly do something. The problem is nobody's measuring the right thing. A new Harness report published this week puts it bluntly: engineering organizations report record productivity gains while simultaneously acknowledging they no longer have the instruments to verify those gains are real. When coding accelerates, PR volume increases, review queues grow, QA saturates, and security validation lags. Throughput only increases when the entire delivery system adapts.

A separate cost analysis from ByteIota found that actual AI tool spending runs $200-$600/month per engineer after you account for everything. Licensing is only 60-70% of true first-year costs. The hidden 30-40% comes from integration labor, training overhead, and usage overages. Microsoft Research found productivity gains don't materialize until 11 weeks, with break-even at 12-18 months.

Meanwhile, a viral r/SaaS post echoed the same frustration from a practitioner angle: pull requests went up fast across teams, but the poster "couldn't take it anymore" watching velocity without quality.

Four different sources. Same conclusion. Faster code generation without end-to-end measurement creates the illusion of productivity.

What builders should do: If you're responsible for AI tool budgets, stop measuring PR volume and start measuring cycle time, defect rate, and time-to-customer-value. The tools aren't broken. The metrics are.