Why did one day of AI cost more than a month of servers?
dxs
15 points
16 comments
June 29, 2026
Related Discussions
Found 5 related stories in 1045.3ms across 14,015 title embeddings via pgvector HNSW
- AI is too expensive crescit_eundo · 135 pts · May 19, 2026 · 60% similar
- When AI Costs More Than the Engineer kiyanwang · 124 pts · July 06, 2026 · 58% similar
- The current AI pricing was always going to go away arnon · 79 pts · May 22, 2026 · 58% similar
- AI costs how much? GitHub Copilot users react to new usage-based pricing system spenvo · 11 pts · June 02, 2026 · 57% similar
- A $20/month user costs OpenAI $65 in compute. AI video is a money furnace Aedelon · 62 pts · April 02, 2026 · 55% similar
Discussion Highlights (6 comments)
ieie3366
The article itself is AI slop.
elzbardico
Really folks. That idea of people without experience and knowledge of software engineering vibe coding production code is a little bit not realistic, no matter how much Claude wants to convince investors of the contrary. Coding agents are fantastic tools, but they are not Jesus: they don't do miracles.
k08200
A big part of the cost explosion is using the frontier model for tasks that don't need to be done. I tried using the gpt-4o and much cheaper models, and the cheaper ones were more accurate in my three — paying for the reasoning depth that I don't use. The other half is asking the model to do what deterministic rules should be. Calls that don't are the cheapest. Starting with profiling what calls the larger model really needs.
initramfs
Very interesting. I am guessing the company didn't offer refunds if the receiving computer wasn't able to process the results, unless the issue was on the service...
mid90sahsan
If this was done by a dev in my company, they would have fired him that instant.
swiftcoder
> A deterministic failure doesn’t get better when you retry it Among all the other nonsense here, this one is solid advice. Most software with retries just blindly retries N times - in reality, you need a retry/backoff policy based on the specific type of error encountered (I've been rooting these out of our own software stack lately)