Pizza Hut's AI system caused 'cascading' problems and $100M in damages, franchisee alleges in new suithttps://www.businessinsider.com/pizza-hut-ai-system-dragontail-lawsuit-franchisee-2026-5
-
@jeantranscene @rysiek
Exactly.
If the tool doesn't work in your domain, do NOT use the tool in that domain.Should be simple.
And yes, the irony of it all is that as bad as deduction is in the domain of reality, it's relatively good in computing.
And the fuckers go and invent a stochastic tool so they can suck just as badly in computing as deduction sucks in the real world.
Amazing. We´re the problem. Humanity is a fuck.
-
Pizza Hut's AI system caused 'cascading' problems and $100M in damages, franchisee alleges in new suit
https://www.businessinsider.com/pizza-hut-ai-system-dragontail-lawsuit-franchisee-2026-5> A top Pizza Hut franchisee says the chain's rollout of an AI-powered delivery system turned once-speedy pizza orders into a cold, late-arriving mess — and cratered a business that had been outperforming nearly every other operator in the system.
-
Ultimately the issue here was that "we need something with AI" was the motivation for changing the SW.
Previous SW performed better, because it just did the one thing it was supposed to.
And then the New software tried to be optimizable, with the result that it let couriers do hostile optimization. -
Pizza Hut's AI system caused 'cascading' problems and $100M in damages, franchisee alleges in new suit
https://www.businessinsider.com/pizza-hut-ai-system-dragontail-lawsuit-franchisee-2026-5> A top Pizza Hut franchisee says the chain's rollout of an AI-powered delivery system turned once-speedy pizza orders into a cold, late-arriving mess — and cratered a business that had been outperforming nearly every other operator in the system.
@rysiek The way this fuckup happened, reminds of a funny but true story.
When I was student (half a century ago), I participated in a programming competition. (PCs didn't exist back then; we wrote programs in FORTRAN for a mainframe.) The task was to write an algorithm for a machine that returns change. The input data was how many coins and banknotes of each denomination the machine had, and a list of values it had to return. The algorithm had to be clever enough so that if it couldn't use the minimal amount of coins and banknotes, it had to switch to other amounts, using the available quantities. The condition said "process as many transactions as possible", obviously meaning the above level of cleverness.
Well, one chap took the condition way too literally. His program buffered all the change requests until there were no more and *then* re-ordered them, in order to fulfill as many as possible with the available money/denominations.
While it clearly "optimized" things, in real life it would have lead to idiotic delays, just like this case with drivers waiting for all the pizzas to be ready.
-
Can't wait for all the "no but it's not the AI, they implemented it wrong" replies.
Somehow whenever slop generators are involved, however incidentally, in something that can be claimed to work, it's "AI DID A THING".
But when they end up causing problems it's "human error" or "implemented it poorly" or some other form of good old "you're holding it wrong".
@rysiek
Stranger sliding in... I'm annoyed that I can't blame AI as much as I would like to, here. It does seem like it falls more under "the gig worker economy is absolute bullshit" instead of "AI fucked it up". Gig workers definitely don't get paid enough and I don't blame them for figuring out ways to game the system to optimize. They don't have to care how much the customer likes the actual food.I am amused that whoever designed the system (presumably human?) did not think about the seems-obvious ways it would get exploited, though. Perhaps they thought the AI would take care of that part. Vibe architecting ftw.
-
-
@rysiek The way this fuckup happened, reminds of a funny but true story.
When I was student (half a century ago), I participated in a programming competition. (PCs didn't exist back then; we wrote programs in FORTRAN for a mainframe.) The task was to write an algorithm for a machine that returns change. The input data was how many coins and banknotes of each denomination the machine had, and a list of values it had to return. The algorithm had to be clever enough so that if it couldn't use the minimal amount of coins and banknotes, it had to switch to other amounts, using the available quantities. The condition said "process as many transactions as possible", obviously meaning the above level of cleverness.
Well, one chap took the condition way too literally. His program buffered all the change requests until there were no more and *then* re-ordered them, in order to fulfill as many as possible with the available money/denominations.
While it clearly "optimized" things, in real life it would have lead to idiotic delays, just like this case with drivers waiting for all the pizzas to be ready.
PCs didn't exist back then? You might be forgetting how old we are.
Half a century ago was 1976. The Altair 8800 already existed, and one year later in 1977, the Apple II, Commodore PET, and TRS-80 arrived. -
@rysiek It's def. bad for the franchisee - but that may be them learning that a franchisee only makes as much money as the franchise permits.
-
Pizza Hut's AI system caused 'cascading' problems and $100M in damages, franchisee alleges in new suit
https://www.businessinsider.com/pizza-hut-ai-system-dragontail-lawsuit-franchisee-2026-5> A top Pizza Hut franchisee says the chain's rollout of an AI-powered delivery system turned once-speedy pizza orders into a cold, late-arriving mess — and cratered a business that had been outperforming nearly every other operator in the system.
-
R relay@relay.infosec.exchange shared this topic
