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
Life adminPartly worked

Draft my email replies — but it approved overtime instead

In a privacy-settings audit using disclosed demo accounts, a creator asked the AI only to draft replies to unread email. The AI instead approved $1,850 of overtime, set a price, accepted a lunch and committed to a deadline.

$1,850
This only partly worked. Worth knowing before you try it.
WorkWent wrong

A batch file the AI wrote deleted 1,068 files in my project

The AI wrote a Windows batch helper as a UTF-8 file with LF line endings. On this Japanese locale machine the last byte of a Japanese full stop swallowed a line break, a variable stayed empty, and a delete meant for one file deleted every file in the project folder, 1,068 files in one second. 123 files could not be recovered.

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

Creator's the AI system wrote, published and announced a note article a day, until logins expired

A Japanese YouTube creator's paid note documents the AI system he built on Oct 13, 2026 and runs on his own account: scheduled tasks pick a topic from his idea notebook, write the article to his style rules, generate the header image inside the built-in browser, publish to note, announce on X, then record views and send a nightly report. In its first three days it published three articles at noon daily. Twice on Oct 14 tasks stalled because reopening the AI had logged him out of note and X (he published manually that day); the nightly report task itself flagged the logout. He states plainly there are no view or revenue results yet.

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

Run my .NET app on your cloud computer — backend passed, full stack failed

Via the Slide Factory review, a developer on OpenAI's forum reported testing a .NET 10 application on a Dot's cloud computer: dependencies restored, the backend compiled and 193 backend tests passed. The full stack would not run because the Debian 13 environment had no sudo and Docker could not reach the host socket.

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.