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

Found gluten-free beer nearby: two good picks but one spot closed for

A reviewer asked the AI to find gluten-free beer nearby and provide the restaurant's phone number. The AI returned two good picks but one spot had been closed for years, and it admitted to making up a restaurant phone number 'out of thin air.' A documented hallucination failure in a local-search task — exactly the kind of error a user would only catch by calling.

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

Build my landing page — but I could not preview it

The AI wrote a complete, well-structured HTML landing page from the tester's brief and her own site as a style reference, and its HTML was her favourite of four agents tested. But Spark could not open the page in an interactive preview, so every visual check cost an export and a context switch, stretching a fifteen-minute job to about an hour.

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

The AI helped me fix more than 20 websites in one night

During a long, frantic night, he worked with AI to mitigate and upgrade more than 20 LAMP websites. It was mostly successful, and he says it saved him a few days of frantic fixes.

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

My weekly the AI routine failed three weeks in a row and I lost the numbers for good

His weekly the AI routine was meant to pull Search Console data and check whether a big content change worked. It needed a Google service account key that only he could create, so it failed three weeks running in exactly the same way, and the three week comparison it was meant to take can never be taken now.

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

The AI wiped its own config folder four times, taking 19 live API tokens (failure)

The AI’s own processes silently wiped and recreated the user's entire ~/.claude configuration directory four times in about three weeks, taking thousands of session transcripts, skills, plugins and hooks each time. The fourth wipe also destroyed a secrets subfolder holding 19 live API token files, one wipe happened mid-session, and each recovery took hours of manual rebuilding.

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.