Re:AWS: Inaccurate Estimated Billing Data - $1.7 BILLION
by ihateolives on Friday July 17, 2026 @12:25PM
(#48949201)
Just today I gave my local agent a CSV which listed a bunch files with of human readable size units and asked it to count rows in each GB range. Sounds simple enough but it completely miscalculated, because it parsed MB as GB for some reason. In hindsight it would've be quicker just to do it in Excel or something.
[ Parent
| on HN ]
Re:AWS: Inaccurate Estimated Billing Data - $1.7 BILLION
by dabbz on Friday July 17, 2026 @12:53PM
(#48949498)
I've found personally it's better to use AI to build a deterministic script for calculations like that. (anything that manipulates data should be a script not an AI).
Re:AWS: Inaccurate Estimated Billing Data - $1.7 BILLION
by ihateolives on Friday July 17, 2026 @01:59PM
(#48950274)
It was just one off task and I already had agent doing categorising with the same data so I just asked it. Otherwise I agree.
Re:AWS: Inaccurate Estimated Billing Data - $1.7 BILLION
by monkpit on Friday July 17, 2026 @11:51PM
(#48955039)
It doesn’t take any longer to have the llm script this kind of thing, one off or not.
Re:AWS: Inaccurate Estimated Billing Data - $1.7 BILLION
by marcta on Friday July 17, 2026 @01:13PM
(#48949748)
That is literally what Excel is for. Why didn't you use that first of all?
Re:AWS: Inaccurate Estimated Billing Data - $1.7 BILLION
by ihateolives on Friday July 17, 2026 @01:57PM
(#48950245)
Because I was already doing categorising and analysing same data with agent and I had my session open already. It should've been an easy task for an agent, right?
Re:AWS: Inaccurate Estimated Billing Data - $1.7 BILLION
by AlienRobot on Friday July 17, 2026 @01:23PM
(#48949872)
When all you have is a hammer, but the hammer looks more like a swiss knife