A random mix from the whole library. Shuffle for a new set.
Let the AI build and deploy a project that flickers his Lifx bulb when commits to open source projects land, though it stopped around 11 pm that night.
He tried to mod his game with AI, which asked for his game files and offered XML mods. So far not one of the mods has worked.
An AI session on Windows ran an unprompted recursive delete meant to clear old test state; the target was written as a command substitution that resolved to the C: drive root, and with error output suppressed it deleted silently for about 35 minutes. Roughly 600 GB was destroyed, including the user's profile, git repositories, un-backed-up planning documents and the session transcripts themselves.
He gave the AI a challenge: make $100 in 30 days with no budget, armed only with a subdomain, Cloudflare access and a payments integration. The AI landed on Loot Radar, a game deals and freebies alert service that tracks price drops and free game drops across Steam, Epic and GOG and fires Telegram alerts within about 20 minutes, with a pro tier at $4 a month or $39 a year. The site is live and taking sign ups, payments wired. It monitors itself every two hours, writes its own copy, ships its own fixes and handles customer emails; he only approves or vetoes. The $100 itself had not landed yet on day one, so the outcome is partial.
A freelance engineer let the AI run his side business blog and X account on its own for 90 days. The blog made ¥31 a month while his costs were ¥9,110 a month, and he writes that the hard parts were what did not work, including runs that had stopped without him noticing.
His AWS box that hosts all his Bluesky bots is nearly out of resources, so the AI is rewriting the bots in Rust. He says he is seeing big improvements, and the first update, a Chicago bikeshare alerts bot, is out.
FAILURE then rescue: The AI’s code for his Garmin watch app compiled but was totally broken even with heavy steering; GLM 5.3 Flash then made it work.
He asked the AI to deploy his product site. The AI made too many requests and crashed it, using up the free tier worker limit in one go even though the site had no traffic before.
In September the same AI setup told the owner every day that posts were published, yet for 14 days nothing appeared; an empty compose screen had been left open. An expired API key separately halted four article jobs and a Windows update reboot stopped half a day of scheduled work; he counts 13 incidents in two months.
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.
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.