Uber torches 2026 AI budget on Claude Code in four months

PessimalDecimal

Is this a submarine? https://paulgraham.com/submarine.html

MichaelNolan

> 95% of Uber engineers now use AI tools monthly with 70% of committed code originating from AI. Well, that’s to be expected when using AI tools becomes relevant in your performance evaluation.

NicuCalcea

Can these AI-generated articles not be prompted to at least cite the primary sources? How do I know any of this is true? Here's a much better article: https://aimagazine.com/news/why-uber-has-already-burned-thro...

woah

It's very easy to blow through hundreds of dollars a session using API tokens especially with the 1m context if you aren't careful about clearing old context. At the same time the subscription will allow the same usage for hundreds of dollars a month. Either Anthropic is absolutely hosing API users, massively subsidizing subscriptions, or a little bit of both.

internetter

I know I'm responding to AI right now, but > which means figuring out if the company can afford this level of productivity at scale. If it was actually productive, then the revenue would increase and affordability wouldn't be a question.

mkozlows

This terrible unsourced article seems to be citing this information piece: https://www.theinformation.com/newsletters/applied-ai/uber-c... ... but the key fact about "$500-$2000" per engineer does not appear there, and seems to be fabricated.

bhagyeshsp

Wonderful, so when will I see novel features in my Uber app?

KolmogorovComp

Honest question, does Uber need that much R&D? And do they expect the ROI to be positive?

jeffbee

It's obvious that the word productivity has been used in this discussion to mean something other than the plain meaning of the word. If AI was productive, there would be no question about whether it could be afforded. If you're asking whether you can afford it then it isn't productive by definition. They are using it to mean a mechanism that produces prodigious amounts of toxic waste. That does not conform to the historical understanding of the word.

abuani

I take a peak every month or so at spend for my company and notice more and more are consumed $1k in tokens a month and it is bewildering to me how. I use llms daily, and see anywhere from $200-$400 tops. This is using the most expensive models, in deep thinking mode. So I'm not a Luddite against the usage of them. I just can't figure how _how_ to burn that much money a month responsibly. I genuinely challenge someone spending $5-$10k a month to demonstrate how that turns into $50-$100k in value. At a corporate level, I'd much rather hire a junior engineer who spends $100-$200/month and becomes productive then try and rationalize $100k/year in token spend.

davidcann

> 70% of committed code originating from AI. How are they calculating that? They could be using my tool, Buildermark, but I do t think they are: https://buildermark.dev

ninjagoo

According to [1], there are about 5500 people in Engineering at Uber. Using $1250 as the mid-point of the $ spend range, that comes to about $6.8 Million in engineering AI spend, ballpark, with the range being $2.75 Million - $12 Million. The article lists $3.4 Billion as the R&D spend. The AI spend does not appear to be a significant chunk of R&D spending (0.3% in 4 months or 1% annualized). If they didn't plan for it, sure, it's not peanuts in the budget, but in context not that much. The real question is, what did they get for that amount? The article claims that 70% of the code commit is now AI-generated, so presumably the code passed review and tests. Did it accelerate the feature count? did it reduce quality problems? Did it lead to other benefits? Sadly the article is silent on the outcomes, besides the higher spend. Maybe 4 months is too soon to assess the benefits. On the other hand, in an agile world ... [1] https://www.unifygtm.com/insights-headcount/uber

AndrewKemendo

This continues to boggle my mind so hopefully somebody can explain how this is happening. I’ve been using all these tools since they started popping out around 2021 personally and professionally. I probably built four or five products at this point with assistance, not to mention the thousands and thousands of back-and-forth conversations for research or search or rubber ducking or whatever. I have never spent more than whatever the professional max plan is that is consistently $20 a month. I asked a friend of mine who spent a couple hundred dollars in like an few hours how they did it. The answer was they basically getting these agent groups of agents stuck in a loop and they’re constantly just generating verbose bullshit that is not even interrogated and doesn’t come out with any artifact that is inspectable no matter how expert you are. The couple of stories I have heard of these massive crazy spends are people literally just assuming these things can complete an entire human task in one shot, so they continue to hit the “spin the wheel” button until they get something closer to what they want But I’ve yet to see that actually work and it actually flies in the face of every instruction guide or documentation or prompt engineering process that has been described over the last almost 5 years

taf2

i bet someone mentioned openclaw one too many times

dataranger

we run an agentic pipeline in a different domain (data sourcing) and the only way the math works is to be ruthless about which stages actually need which model. As a founder, the question I always have is "what is the marginal value per token relative to engineer-hours saved." More of a gut feel at the moment, but would be great to calculate.

hyperpape

I love how these articles drop, and all of a sudden HN is filled with people who think engineering productivity is simple to measure. Yes, productivity implies revenue (or cost reduction), and revenue is measurable. However: 1. You spend money today to build features that drive revenue in the future, so when expenses go up rapidly today, you don’t yet have the revenue to measure. 2. It’s inherently a counterfactual consideration: you have these features completed today, using AI. You’re profitable/unprofitable. So AI is productive/unproductive, right? No. You have to estimate what you would’ve gotten done without AI, and how much revenue you would’ve had then. 3. Business is often a Red Queen’s race. If you don’t make improvements, it’s often the case that you’ll lose revenue, as competitors take advantage. 4. Most likely, AI use is a mixture of working on things that matter and people throwing shit against the wall “because it’s easy now.” Actually measuring the potential productivity improvements means figuring out how to keep the first category and avoid the second. This isn’t me arguing for or against AI. It’s just me telling you not to be lazy and say “if it were productive you’d be able to measure it.”

jcgrillo

AI token austerity when

tunesmith

I think as it becomes more common for executives to think we can replace software engineering with agents, I wonder if they might be basing their decisions off of unrealistic perceptions of the average software engineer. I guess I'm mulling two somewhat contradictory senses: 1. You get out of it what you put into it. A savvy CTO might be incredibly excited by everything they can do with agents, and improperly think that all the software engineers can do the same thing, when in reality your org's average software engineers might not have the creativity to even think of many cases where it could save them work. So by mandating agent usage, you might find that productivity hasn't improved while AI costs have increased. 2. When using AI, there are two gaps that become more obvious. First is the gap of: who tells the agent what to do? In many orgs, product isn't technically savvy enough to come up with a detailed spec/plan that LLM can use. And many cog-in-machine developers aren't positioned to come up with the spec, they just want to implement it. By expecting work to be implemented by agent-using developers, you might instead find a lot of idle workers waiting for work to show up. Second is the qa/review cycle. You've introduced a big change to the org but are you really saving cost or shifting it? I'm all for introducing LLM as optional to help existing developers increase velocity and quality, but I think the "let's restructure the org" movement is really dicey, especially for mid-size or smaller employers.

saos

Interesting. Some companies have rolled it out to every department with a small budget. I wonder how this will end as AI becomes more expensive to use. If you can't quantify ROI then I guess you're cooked.

uncircle

Now AI slop factories make the HN front page?