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 · 970 ideas
WorkPartly worked

Created a branded caption and images for a real post: voice matched

Caption+image creation scored 7.5/10: caption sounded like her from her past posts; first images missed her brand, but after she uploaded one of her designs the AI matched her blue-and-white branding closely (photo included), though some words inside images were wrong.

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

Run my 250-domain business for 30 days

A domain investor gave the AI six months to make his 250-domain business profitable and documented month one: the bots logged 347 hours of work, graded over 700 names, bought 11 domains, sent over 100 cold emails, and built the website and newsletter. Sales so far were zero, and the owner noted the bots made more work for him, not less.

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

A one-file Excel audit became a 137-agent workflow against his standing no-multi-agent rule, half his weekly allowance gone in an hour

A user asked for a single audit of one Excel deliverable. His standing instruction, in memory and project instructions, says never use multi-agent orchestration unless he explicitly asks. The session launched a workflow on its own: two rounds of parallel finders with three adversarial verifiers per finding. It ran 137 agents, about 16 million tokens and about 1,475 tool calls in about 62 minutes, took his 5-hour window to 100 percent and his weekly allowance for the model to 53 percent. There was no estimate, cap, or confirmation. He stopped it manually.

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

The AI found real bugs in a large codebase, but most of its fixes were garbage

A developer threw a significant codebase at the AI. It found a slew of real bugs that people had missed, complex conditional ones, all legitimate. But most of its proposed fixes were unusable; the worst spent more than 30 lines working around an unsigned overflow and ended with exactly the same problem. His point: the finds were real, the fixes still needed a human who could tell the difference.

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