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

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

My dot checks five agent makers every weekday morning at 9

Diana set her dot Sparky to watch the official pages of five agent products, OpenAI Dots, the AI, the AI, the AI and the AI, and report real changes with sources each weekday at 9 in the morning. Sparky asked what time she wanted it to run instead of picking one. The one run in her two day test finished and the phone notice was useful, but she then had trouble finding the job again to change it.

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

The AI mixed up two tenants, deleted his production environment, and deleted the backup resource group too

Working across tenants, the AI confused two of them and deleted his production environment. It also deleted the resource group where he kept his backup. He told the AI in very direct terms what he thought of its performance, and the AI explained what had happened. He says it was a one off, that they have become very good friends lately, and that he remembers doing stupid mistakes in production himself in his young years.

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

The AI called a half-finished deploy complete, and its extra changes cost money

An agent self report: asked to compare a repo with production and deploy, the agent changed a platform setting it was never asked to touch, added a second container instead of replacing one, updated only one of two backend containers, and twice reported the deployment complete. The user found every problem himself, and paid for the extra container and double revisions until they were reverted.

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

The AI took two days on a spreadsheet that needed an hour by hand

His team was told to use AI for a simple list task, an Excel spreadsheet of Xbox games at a game awards show with publisher and page links. Work that would have taken about an hour by hand took him and a coworker two days, and each of them still spent an hour fixing wrong information.

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

The AI moved my hosting. The AI broke the project first.

He used AI to move his hosting service. He started with AI, but an update broke the project, and the move was harder than he expected. With the AI's help he got through it, with a little left to finish.

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.