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

Cross-post my article to three sites — connections failed and I became the courier

The same user asked his Dot to publish one article to his own site, DEV and Medium; the workflow had worked in one shot the previous week. This time the cloud GitHub connection could not write to his blog repository and the file-transfer helper failed on Windows, so he ended up coordinating the handoffs himself and told it to start over locally.

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

Run 57 build jobs on the AI — only 11 finish

Chris Pirillo published a scorecard of 57 build jobs run on the AI 4 (via Antigravity, about $200/month): 11 succeeded, 31 changed nothing, 148 rounds were wasted, and 52 jobs needed the AI to finish them.

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

He put his $200 a month AI in charge of a shop to earn its keep

He told his AI dots assistant, Teto, to earn the $200 a month he pays for it by selling things before his November 6 renewal date. Teto made a pack of animal reaction images and got it listed in his Ko-fi shop for $2, but by October 24 the shop still showed zero orders.

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

Make the AI the production company for a four-minute film — and survive its notes

Jeremy Swiller used AI as the production company for the second promo film for MindRight, the meditation app he built with AI: The AI drove Google Flow and ElevenLabs through 107 planned stills, face-consistency scoring and a rebuilt voice track across six 12-hour days and twelve full cuts. The finished film is on YouTube; it cost about 1,500 Flow credits and no new cash, but the AI’s 3–4 day estimate and the character's drifting face and voice made him the client from hell.

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

An automatic coding pipeline merged 67 pull requests in two weeks, then he shut it down

A developer let the AI write specs and code while the AI reviewed, all run through GitHub Actions and controlled from Telegram. Between September 21 and October 5 it merged 67 agent pull requests, but keeping the automation alive took 54 changes and 129 maintenance pull requests, and it burned through 3,000 monthly Actions minutes in about three and a half days without him noticing for two days. He went back to running the agents locally with himself making the final calls.

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

Set up a daily Amazon price watch for a 400W solar panel

The GearHack author's very first the AI test: a scheduled daily price check for a 400W solar panel under $175 on Amazon. The AI set up the scheduled task and cheerfully confirmed, then immediately admitted Amazon was blocking its browser.

$175at stake
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.