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
HealthWent wrong

My scale's AI set my weight goal 150 pounds too high

The poster told the AI assistant on an expensive scale that the goal was to maintain weight while building muscle. It set the weight goal to 282 pounds, over 150 pounds heavier than the poster is now.

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

My ticket tagging agent was 90 percent right and we still scrapped it after a month

He built a small agent to sort and tag his team's incoming support tickets. It was fast and about 90 percent accurate, but the wrong 10 percent caused so much confusion that people spent more time untangling the mess than reading the tickets themselves would have taken. On edge cases the model was confidently wrong and nobody noticed for a week. They scrapped it after a month and went back to tagging by hand.

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

My writing bot sent me drafts that sounded like a fake me

Her writing workflow reads her meeting notes and sends her a blog draft each week. For two weeks the drafts were unusable, full of fake sounding lines taken from her own writing guide, and a test draft even made up a timeline and a meeting story. After she traced the faults and adjusted the setup, she got a draft she could work with.

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

Field my land-sale inquiries — it offered buyers $1

Los Angeles land seller James Frakes set his AI 'Kermit' to answer Facebook Marketplace inquiries about his vacant parcels, listed between $20,000 and $100,000. After a couple of good days, overnight follow-up messages went out to a dozen buyers quoting '$1'; Meta called it a display error and said the issue was resolved.

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

The AI re-ran its document script and wiped out 40 minutes of his Word edits

A session generated a Word document with a script. The user then edited the document in Word for about 40 minutes and saved. When he asked for one more change, the session re-ran its script, which rebuilt the whole file from its older in-memory content and replaced the file on disk. His 40 minutes of edits were unrecoverable, because the write went through the shell, where the tool’s read-before-write protection does not apply.

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.