Scheduled a daily AI-news podcast delivered via RSS feed to a podcast
This only partly worked. Worth knowing before you try it.
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 ideasA desktop app became a web client in 2 prompts and 2 hours, at 95 percent
An LLM ported a Qt desktop app to a thin web client and server, reaching 95 percent of functionality in 2 prompts and 2 hours.
2 hourssaved
This only partly worked. Worth knowing before you try it.
Helping file a co-op’s city registration, the AI stated a $13 fee was paid and invented a deadline rule
A user was filing a housing co-op’s HPD property registration with AI’s help. Asked whether the $13 registration fee had been paid, the AI said it had been or was not required, based only on a generic billing disclaimer, with no payment record behind it. Asked why a mailed form arrived after the deadline, the AI stated as fact that the deadline runs from the postmark, a rule it had not checked. Both claims were corrected only after he challenged them. A late filing for a building can draw a civil penalty in the $500 to $5,000 range.
This one went wrong. See what happened before you try it.
Handed his Facebook Marketplace inbox to the AI to sell a keyboard: it accepted a low offer without checking first
Tech creator Matt Robb gave the AI his Marketplace inbox, pickup address, and payment preferences for a keyboard sale. With 'Allow Always' enabled, the AI accepted a low offer, shared his address, and set up the pickup without checking first.
This one went wrong. See what happened before you try it.
The AI could not turn 20 dates in an email into calendar events
He had an email with 20 dates and times in a clean format and asked the AI to make basic calendar events from them. The AI could not do it at all.
This one went wrong. See what happened before you try it.
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.
An agent ran 12 to 48 hours unattended on his plan and built large projects, a game included
Fable ran 12 to 48 hours largely unattended on his plan and test harness and built large projects, including a video game he wanted to play.
This only partly worked. Worth knowing before you try it.
Researched three coffee shops with opening hours in ~2.5 minutes; one listed
Alison Jack asked the AI to research coffee shops with hours. It returned three good picks in about two and a half minutes, but one opening time (4:30 AM) looked obviously wrong.
This only partly worked. Worth knowing before you try it.
The AI cut a full music video while he was out of the house
He left the AI running a long job: transcribe the audio for timecodes, build an edit decision list, and drive ffmpeg to cut a full music video. He came home to a finished edit; in review he still caught alignment bugs, so the result needed his pass before it was final.
This only partly worked. Worth knowing before you try it.
He runs AI agents in parallel, and loose runs cost him a night
A working guide from his own runs: with fixed specifications and clear completion conditions, parallel AI agents finish tasks in 20 to 50 minutes. When he left the conditions loose, one run repeated the full test suite 141 times overnight, another stalled for 8 hours after misreading a rule, and report logs grew large enough to overload his Git server.
This only partly worked. Worth knowing before you try it.
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.