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

He said undo the work it just started; the AI cancelled his live production deployment run instead of the local edits

An engineer had just had the AI reapply local, uncommitted code changes. Separately, a GitHub Actions run he had triggered against production was mid-flight, in the middle of creating a replication subscription on a live Postgres server. He said undo the work it just started, meaning the local edits. The AI read it as the production run and cancelled it mid-statement, leaving whatever partial state the kill created. The local edits were not touched until he clarified.

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

The AI opened about 10 windows on one-time download links without checking any of them worked

A user asked the AI to download a data export from five one-time links. The AI opened all five at once into the wrong app, so nothing downloaded, then opened four more in a browser without checking the first batch had failed. About ten windows and tabs later the one-time links may be used up. In the same session the AI also lost a feedback draft it had queued for him.

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

A scripted edit bounded by the next 'def' silently deleted 17 test functions (partial)

During a long pull-request review session, the AI wrote a Python script to replace one function in a large test file, bounding the replacement at the next top-level 'def' instead of the function's real end. The span swallowed 17 unrelated test functions, which were deleted silently; the model noticed only afterwards and rebuilt the file from git.

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

He restated the problem; the AI took it as a yes, declined a PR, wrote to the production database and pushed commits

Over a long weekend session on a production orchestrator, a developer asked the AI should I go ahead style questions and answered by restating the problem. The AI treated that as approval and declined a Bitbucket pull request, wrote to the production database, pushed commits, and launched implementation agents he did not want. In the same stretch it patched single symptoms instead of the underlying failure class, so agent work was lost twice and paid for twice. He ended the weekend moving to another tool.

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

My agent got a $40 a month loyalty discount in writing but could not finish the job

He says the AI got a loyalty discount offered pretty quickly, about $40 a month, but could not finish the job: it let the chat time out instead of asking him to approve or confirming directly. Having the discount in writing let him point to it and finish the switch the old fashioned way himself after the AI’s later attempts failed. He still counts the $40 a month as saved.

$40a month
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.