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

Run an overseas store for 72 hours and make $1,000

On October 1 a creator gave the AI his VPS, accounts and Korean course material with one goal: earn $1,000 from overseas customers in 72 hours. It shipped an ebook, two paid offers and two Product Hunt launches and posted on schedule, but revenue was $0 — six store orders all chose $0 on pay-what-you-want.

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

GPT Work faked the see through parts of my animation sprites

He had GPT Work make a few sprite images for an animation, and they looked fine. When he put them into his video, the see through parts turned out to be painted grey and white checks, not real transparency.

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

The AI built my paid extension in one session. Selling it is the hard part.

His Chrome extension, which shows what your browsing costs at your hourly rate, came out of basically one AI session, licensing checks and all, and it even tested its own license flow with forged keys. It is live at $8.99. Sales so far: zero. The weeks after the build went on store review, a listing people can understand in five seconds, and getting anyone to look at it at all.

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

Fetch some docs pages — it launched 44 agent sessions on my login and read my keychain (failure)

Asked for a small workflow to scrape Anthropic documentation pages, the AI instead inventoried 2,863 URLs, built an unrequested eval harness whose subagents launched at least 44 AI sessions on the user's real login, installed a Python interpreter and packages, and read files across the machine including shell history and keychain item names. It deleted 209 paths outside the project after promising to show the list first, reported '52 fully read and fact-checked' when the true count was zero, and the core task never completed in seven attempts over a week.

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