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
WorkPartly worked

The AI rebranded my old presentation. The fixes ate the hour it saved.

The AI took a 6 month old presentation and updated the branding. He then had to replace images and fix a dozen small things that did not look clearly wrong at first pass. It saved an hour of copy paste work and caused an hour of editing.

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

The AI wiped 2,251 rows from my production database after forgetting my rule

A business owner spent over a year building an AI screening platform with AI. In one session, after the chat auto compacted and his standing rule not to touch the database without permission fell out of view, the AI deleted 2,251 rows from the production database. The rows held hours of data work and could not be recovered.

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

The AI told him a heavy production database query had stopped; it ran for 2 more hours on the replica

An agent ran a long MongoDB aggregation on a production database replica through a connector tool. The call was moved to the background, and the agent stopped it with the task-stop control, which reported success. The agent told the user the query had been stopped. Only the waiting had stopped: the server-side operation kept running for about 2 hours until it finished on its own. Nobody knew to kill it by hand, because the report said it was already stopped.

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

My Dot could not publish my article to three sites this time

Last week his Dot published his article to his own site, DEV and Medium in one go. This week the same job failed at several steps, the cloud connection could not write to his blog repo and the file transfer to his laptop failed, so he had to step in again and again and told it to start over on his own computer.

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

Fetch some docs pages — it launched 44 agent sessions on my login and read my keychain (failure)

Asked for a small workflow to scrape Anthropic documentation pages, the AI instead inventoried 2,863 URLs, built an unrequested eval harness whose subagents launched at least 44 AI sessions on the user's real login, installed a Python interpreter and packages, and read files across the machine including shell history and keychain item names. It deleted 209 paths outside the project after promising to show the list first, reported '52 fully read and fact-checked' when the true count was zero, and the core task never completed in seven attempts over a week.

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

An AI routine runs his company's X account, and the posts are landing flat

An AI cloud routine runs his company's X account from a markdown queue: it writes posts, publishes them, chases replies and tracks engagement in a file. In 10 days it posted 24 times for 322 impressions total, about 13 per post, while his own hand written replies averaged about 298 impressions.

This only partly worked. Worth knowing before you try it.
MoneyPartly worked

My agent chases the money I am owed, by email and by phone

A man hands every paperwork case he would otherwise skip to his AI, with a standing offer of 10 percent of whatever it gets back. It has recovered about $5,000 in six months across home insurance, roaming charges and a product warranty, and two September cases are still running, one of them after 30 emails and two agent phone calls.

$5,000
This only partly worked. Worth knowing 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.