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

Build and deploy a public status dashboard that updates itself

Amplifying.ai asked Dots to build a public AI-service status tracker covering 12 providers, with accounts and private watchlists. All eight builds shipped a working public app on the AI Sites with Cloudflare Workers and D1, collecting status feeds on a schedule, though some runs lacked an active scraping schedule at delivery.

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

My first model designed with AI 4 is a popcorn bucket

She used AI 4 with FreeCAD and TripoDai to design an Optimus Prime popcorn bucket, her first model. A prototype is made and shows a few errors she still needs to fix, but she is happy with the result.

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

Quoted a September 15 Amazon delivery date when the same item was

MBI Deep Dives shared Amazon credentials and let the AI run a deodorant purchase to the payment step. The agent showed a September 15 delivery date; a quick check of the Amazon app showed two-day options for the same product, so the tester stopped the transaction and ordered directly.

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

The AI rescued my old blog and every Linux Journal piece I ever wrote

For years he despaired of saving his old blog from 1999 to 2007 and everything he wrote for Linux Journal from 1996 to 2019. He asked the AI for help, and the AI rescued both sets of writing and put them back online at searls.com, though some Linux Journal pieces are still missing.

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

Solo operator ran his whole business on 14 the AI scheduled tasks for 30 days

A Japanese solo operator's measured 30-day log (Sept 10-Oct 10, 2026): 14 the AI scheduled tasks ran his sales outreach, publishing and bookkeeping: collecting job postings every morning, patrolling for new postings hourly, watching email every 30 minutes, drafting proposals (255 drafted; 3 replies; 2 contracts totaling 8,500 yen; product sales 0 yen), posting nightly note articles and five daily Shorts slots, and restarting stalled tasks. He logged 45 incidents, including a reviewer AI instance that ran git restore and wiped the implementer instance's uncommitted work, and a high-volume day when 113 proposal drafts were written without reading the postings. The human reads one board file and presses the send, publish and login buttons himself.

¥8,500
This only partly worked. Worth knowing before you try it.
WorkPartly worked

Agents read 206 of my AI sessions and found 223 failures

Haiku 5.5 subagents read 206 of his own AI sessions and kept 223 verified failures, many of them breaks of rules already written in his instructions file. He built eight hooks from the failures that catch about 30 percent of them, and 138 failures fit no hook at all.

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.