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
HomeWent wrong

The AI replaced Assistant and my smart plugs barely work now

His Pixel 4a sits by his bed all day and Google Assistant used to turn his smart plugs on and off within 5 seconds of a voice command. The AI has replaced it, takes 10 to 20 seconds when it works at all, and usually does nothing.

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

My bot got my Albuquerque parking ticket sent to be voided overnight

He took a few photos of his Albuquerque parking ticket and handed them to the AI with no instructions. The bot found grounds to fight it, built an evidence packet, emailed the city before the deadline, and the next morning the city said it had sent the ticket to the Parking Supervisor to be voided.

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

My agent turns my streaming services on and off on a schedule I approved

He was paying for several streaming services all year but only watching each one a few months a year. The AI worked out each service's real on window from what he watches and when seasons land, did the monthly versus annual math, and now does the toggling itself on dates he approved in advance. Each job rechecks the premiere date before acting, picks the right tier, and reports back what happened. If a cancel fails it tells him instead of retrying forever. Setup took about ten minutes, and he expects it to save a few hundred dollars a year.

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

My scale's AI set my weight goal 150 pounds too high

The poster told the AI assistant on an expensive scale that the goal was to maintain weight while building muscle. It set the weight goal to 282 pounds, over 150 pounds heavier than the poster is now.

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

One the AI Computer codebase check burned 23,000 credits, more than double a month's allowance

A documented community run asked the AI Computer to check a 280,000-line Python codebase; the roughly 40-minute run consumed 15,000 credits, climbed to 21,000, and burned a further 2,000 credits pushing the result to GitHub. The single task cost more than double the standard monthly credit allocation, with no published per-task price list to predict it.

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.