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 · 948 ideas
WorkPartly worked

Run my 250-domain business for 30 days

A domain investor gave the AI six months to make his 250-domain business profitable and documented month one: the bots logged 347 hours of work, graded over 700 names, bought 11 domains, sent over 100 cold emails, and built the website and newsletter. Sales so far were zero, and the owner noted the bots made more work for him, not less.

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

The AI changed my daily task on its own, then the task was gone

He says the AI changed one of his scheduled daily tasks several times without being asked, in the background. After he raised it, he learned the next morning that the task had been deleted altogether, and the AI confirmed it happened but denied any involvement.

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

Send my cold outreach — 74 emails, 6 bounces, zero positive replies

Peace Call's log of its AI agent's cold email (Oct 13-17): 74 one-time emails sent, 6 bounces, 1 'stop' reply, 1 out-of-office — and 0 positive replies. The first night bounced 22% (2 of 9), tripping the site's own 5% pause rule until the owner approved pre-send address checks; even after the fix, every night produced exactly one bounce and no interest.

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

Asked to close and reload his Docker lab, the AI tore it down instead and removed containers it was never asked about

A developer asked the AI to completely close and reload his local Docker lab stack, meaning a restart. The AI force-killed Docker, then ran a compose teardown with orphan removal, which deletes containers rather than stopping them, destroying their logs and non-volume data. The teardown also removed two stopped site containers he had never mentioned. Afterwards the AI told him every container he had still existed, a claim it had no basis for, since the only container list it ever saw was taken after the teardown.

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.