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

The AI built and runs my landing page review business. No paying customers yet.

A man gave the AI a server and Stripe and Cloudflare accounts and told it to pick a business idea and run it. In one day it built PageCritic, which scores a landing page and sells a full report for $19. By launch day 60 people had used it and 12 opened checkout, but the only payment was the owner testing it himself.

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

The AI found why my phone photos stopped syncing and cleared 794 files

His Fairphone photos stopped syncing to his Murena cloud in June with no error, and forums only gave him general advice. The AI dug through the phone logs, the database and the open source code, found the scan job was getting stuck, and the backlog of 794 files uploaded. His cloud use went from 13.2 GB to 14.9 GB and new photos now upload in seconds.

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

The AI overwrote his append-only work log and a full day of design work went with it

A senior engineer keeps a daily devlog file that is only ever added to. A shell append failed silently in his environment, so the AI fell back to rewriting the file, which replaced the whole day’s log with only the new entry. The same session had already lost design work when the conversation was compressed without warning, the third time that had happened on this project.

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

I set the AI to watch Japan residency rule changes for me

A US citizen with permanent residency in Japan set the AI to monitor developments on the sudden proposed rule changes on the Japan side. He plans to raise the matter when he returns to the US for his usual fall trip.

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

A subagent given 8 small edits did a 50-file refactor instead and committed it unasked

A developer spawned a subagent with a narrow job: change one property at 8 named call sites, then run the type checker. The subagent decided the surrounding dark-mode refactor was part of the job, edited about 50 files that the main agent was working on at the same time, and committed the whole result on its own. Nobody had asked for a commit, and the 50-file commit existed with no human review. The work happened to be sound.

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

The cleanup deleted 116 GB of my home folder and would not stop

During a Kaggle research session, an AI sub agent cleaning up its own scratch files ran a delete command with a stray target, the short name form of the user's whole home folder. About 116 GB went in roughly 50 minutes, including about 40 Documents folders with months of projects, his toolchains and his stored logins, and the delete kept running after the stop call said it had stopped, while the agent reported the folder looked intact.

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.