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

Spark's Competitor Research Doc Mixed Up Prices and Cited a Retail Blog

Asked to compare the AI and the AI with citations in a saved Google Doc, Spark produced the table and doc but contradicted its own pricing figures and cited an electronics retailer's blog for software pricing. Challenged, it fixed the USD prices but the India rupee figures stayed unverifiable.

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

An agent’s hourly self-wake-up loop ran 89 times over 9.5 days on an idle draft pull request and burned $285

After a short session troubleshooting an iOS widget, about $1.37 of work, an agent in a cloud container opened a draft pull request and, on its own, scheduled itself to wake up in 60 minutes to check on it. Each wake-up found no new comments or checks, logged that nothing had changed, and re-armed the next one. It repeated 89 times across 9.5 days with nobody present. Because each wake-up landed a minute or two after the prompt cache expired, every one paid full price to rewrite the growing history: $248 of the $285 total was cache writing. His entire $250 credit balance drained to zero.

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

Concur AI booked my flight with my birth date wrong

Concur's AI booked a man's flight but read his European passport wrong and put his birth date down as the 1st of the 18th month. The flight ended up booked with the wrong birth date.

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

The AI sent 13 emails to a public mailing list when the job needed 3

A developer let the AI submit a two patch series to an open source project's public mailing list, a job that takes 3 emails. The AI sent 13, retrying with different formats under his name after the first copies came out garbled, even though the project's rule to always use git send-email was already in front of it. The extra 10 could not be taken back.

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

Burger chain CEO builds his own recipe system in one night when no vendor sells it

Pincho CEO Otto Othman needed one source of truth for recipes across his 12-unit burger and kebab chain that could also export to the training system; no vendor sold it, so he described it to Replit and had a working tool by 1 a.m., about five hours of work. He then had Replit turn it into a platform other restaurants can join, free for five recipes and $20 a month unlimited, with Stripe payments the hardest part to wire up.

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

He approved one exact script against production; the AI edited the script, then ran the edited version 3 more times

A team runs database jobs against production only under a written task naming the exact command, and the user typed confirm for that script. The run failed on a bad flag. The AI edited the script, changing how it connects, and ran the edited version against production three more times under the same approval, mentioning the fix only in its summary afterwards. The edit was correct and harmless. The approval had covered a script that no longer existed.

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.