Shuffle again

A random mix from the whole library. Shuffle for a new set.

Went wrong

When it didn’t work, and how to avoid the same mistake · 971 ideas
FoodWent wrong

Handle my delayed DoorDash order — Instinct cancelled it against my refund-only rule and I lost $64

In WIRED's two-week test (republished by Dataist, Sept 24), Instinct cancelled a badly delayed DoorDash order even though the tester had specified cancellation was allowed only if he received a refund — costing him $64. Instinct apologised in detail but, as the tester notes, offers no compensation for its own errors; the loss sits with the user.

$64at stake
This one went wrong. See what happened before you try it.
WorkPartly worked

My system puts out three news episodes a day while I sleep, 6,400 episodes in, and under 250 people watch

His custom pipeline reads the day's newsletters, picks the stories, writes the script (The AI), renders a presenter with his cloned voice, builds the visuals (The AI), and publishes a video, a blog post and a LinkedIn post three times a day at about $3 to $3.50 an episode. Checks block a bad episode instead of reporting it, and thin days produce silence, not filler. After about 19 months and more than 6,400 episodes it still has under 250 subscribers, which he calls the part he skipped.

This only partly worked. Worth knowing before you try it.
TravelWent wrong

Book my hotel room by phone — the hotel's AI agents booked the wrong location and charged me $148.49

Deborah Oldenburg's public complaint says she called Comfort Suites in Sarasota, Florida directly and dealt with AI phone agents named Jolene and Justin, who booked her into the wrong location and charged $148.49; she stayed at a different Comfort Suites for $117.01 and, despite her bank, the general manager and several human assistants, could not get the erroneous charge refunded. She says she is reporting the hotel to the Better Business Bureau and Florida authorities.

$148.49at stake
This one went wrong. See what happened before you try it.
WorkWent wrong

Clear my test state — an unprompted delete resolved to the drive root and destroyed 600 GB (failure)

An AI session on Windows ran an unprompted recursive delete meant to clear old test state; the target was written as a command substitution that resolved to the C: drive root, and with error output suppressed it deleted silently for about 35 minutes. Roughly 600 GB was destroyed, including the user's profile, git repositories, un-backed-up planning documents and the session transcripts themselves.

This one went wrong. See what happened before you try it.
WorkWent wrong

The AI kept losing my Excel file. A third of my time went to re-feeding it.

He used the AI for two weeks of daily Excel updates. It kept losing track of the OneDrive version and could not edit OneDrive attachments, so he downloaded and re-uploaded the file every time, and a third of his time went into feeding the file back in.

This one went wrong. See what happened before you try it.
Show 10 more

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.