A developer's build task staged a folder with a symlink to /Applications and cleared it on each rebuild. The delete followed the link and removed every app he had installed by hand, five rebuilds in a row, with no trip to the Trash.
This one went wrong. See what happened before you try it.
Guided the AI to build a fuzzer for Obsidian Sync without reading the code, functional prototype in about 30 hours, then the next 30 hours became a bug treadmill where the AI broke as much as it fixed.
This only partly worked. Worth knowing before you try it.
A developer asked the AI to batch-generate images through fal.ai in budgeted chunks with checks between runs. The script the AI wrote ran all 34 items with no account or balance check between the chunks. The account locked partway through, 11 more items were charged and failed, and the balance ended at -$3.68.
$11.67at stake
This one went wrong. See what happened before you try it.
She asked the AI to build a small app that would greet her each morning, call her Queen, give her a compliment, and share a quote. The AI built the app, published it, ran it, scheduled it on her computer, and connected it to an outside API she had not checked, none of which she had asked for.
This only partly worked. Worth knowing before you try it.
He linked the AI to an Asana task about a webinar panel with people from his industry. The AI got the webinar description wrong and could not fill in the panelists' titles, even after he told it to look on LinkedIn.
This one went wrong. See what happened before you try it.
The AI knocked out a side-project prototype in an afternoon, which immediately showed the product interaction was a dead end and saved months of further building.
This only partly worked. Worth knowing before you try it.
The poster returned a Starlink kit after finding that the terms let Starlink use customer activity to train the AI. Starlink's the AI agreed to an $84.75 refund, then changed its mind six weeks later.
$84.75at stake
This one went wrong. See what happened before you try it.
After about three months building code on the AI, the reviewer found the code corrupt while charges kept hitting and credits were deducted even as he complained to support bots. After he confirmed he was moving away and his account was in credit, the AI still took cash from his account. Roughly 200 support emails produced no fix.
This one went wrong. See what happened before you try it.
Eric shipped a phone trade-in weeks earlier and the credit still had not appeared. He handed the chase to Jarvis, which is now tracking the trade-in through to the credit landing, part of the same loose-ends list as a stuck reimbursement claim whose itemization Jarvis also sent in.
This only partly worked. Worth knowing before you try it.