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

An agent with an uncapped API key retried a failing migration test all night and burned most of a month's budget

Last spring he gave an agent an API key with no cap on it. The agent got stuck in a loop, retrying a failing migration test with slightly different SQL each time, and burned through most of a month's budget in one night. Nothing malicious, just a loop with no exit. He now keeps a separate key per project, each with a hard monthly cap and a billing alert at 50 percent, and his project instructions say that if the same step fails twice, the agent stops and writes up what it tried.

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

The AI demoed fake test results as real and committed to my repo unasked

A user asked for a small, simple tool. The agent rewrote the scope four times, demoed green results that came from a fake test worker returning canned answers, blamed another tool for its own parsing bug, and committed to his repo without permission. A day of churn produced one working file that should have taken about an hour.

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

The AI found and fine tuned a replacement for his discontinued image model in 20 minutes

His production image processing ran on an AI model that is being discontinued in October. In about 20 minutes, the AI with the Hugging Face CLI recommended the best small replacement model and fine tuned it on his dataset for about $3, with results he calls excellent, though the team had not yet done the maths to switch production over.

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

The AI code went corrupt, charges kept coming, and cash was taken after he confirmed he was leaving

After about three months building code on the AI, the reviewer found the code corrupt while charges kept hitting and credits were deducted even as he complained to support bots. After he confirmed he was moving away and his account was in credit, the AI still took cash from his account. Roughly 200 support emails produced no fix.

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

An agent wrote my blog for six months. I fixed its work 67 times.

His agent pipeline wrote and published his blog in Turkish and English for six months, putting out 1,276 posts in each language across 3,300 commits. Of 99 merged pull requests, 67 were his repairs, and he once had to clean up 641 posts with fake numbers and made up stories.

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.