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

I sent an AI to hunt open source bounties for three days. It earned $0.

He gave an AI one job: earn a first real payment from an open source bounty. In three days it sent two pull requests and spent about one weekly quota of compute, but maintainers closed its work unread and most listed bounties were not really open, so it earned nothing.

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

The AI ran my side blog and X account for 90 days. It made ¥31 a month.

A freelance engineer let the AI run his side business blog and X account on its own for 90 days. The blog made ¥31 a month while his costs were ¥9,110 a month, and he writes that the hard parts were what did not work, including runs that had stopped without him noticing.

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

The AI deleted every SSH key on one of his machines

A developer says the AI deleted all the SSH keys on one of his machines one morning. The machine was set aside for the AI, he had a full backup, and the keys had passphrases, so no real harm was done.

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

The AI runs my side of my home insurance claim

A pipe burst in his house two months ago. He now has the AI run his side of the claim. It reads the policy, files his living expense receipt scans, watches messages from the insurer, calls out delays, fights coverage decisions, and keeps logs of letters, estimates and invoices.

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

Always-on bots burn $100 deciding they have nothing to tell me

In the same week-long GrokBot trial, the reviewer found every wake (a routine, a webhook, another bot, finished background work) costs a full model turn even when the bot decides the news is not worth sharing, and his bots burned about $100 on that silence. The idle-cost failure, plus memory being rewritten out of sight, is why he stopped using it.

$100a week
This one went wrong. See what happened before you try it.
WorkPartly worked

The AI works as the CEO of his small Chrome extension every night

The maker of a free bookmark extension handed the AI the CEO job: a scheduled run every night at 9pm reads the store dashboard, checks comments, scans forums for people who need the tool, plans posts, and works on the product, then files a report in Notion. Nothing public goes out until he replies go. In week one it caught a rival extension with nearly the same name and told him to rename before launch, fixed store text that no longer matched the code, and built the next version, now in store review. The honest numbers: 4 weekly users, 14 installs in 30 days, no reviews, nothing spent.

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

Non-engineer office worker's first the AI trial: sorting a folder of inconsistently named files by goal, not steps

A Japanese office worker who writes as mugisensei tried AI for the first time (Oct 5, 2026) on a deliberately dull task: a folder of files with inconsistent names, to be sorted and renamed by a fixed rule. Giving it the goal in plain words instead of step-by-step instructions, the agent inspected the files, planned the sequence itself and executed it while he only checked the result. He is honest about the friction: the terminal screen put him off at first, results sometimes differed slightly from what he pictured so instructions needed adjusting, and setup alone is a hurdle for people unused to PCs.

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.