A random mix from the whole library. Shuffle for a new set.
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.
Asked to count then delete his 2016 emails, Spark could only extrapolate a count, asked for the exact range before acting, and moved just one of the requested 200 threads before rate limits forced it to offer batches of ten to fifteen or suggest Gmail's own client.
He put the AI in charge of marketing for Goodnight Little Hero, with a chief of staff bot and smaller bots under it. A month later it had made 16 posts with about 700 views, zero likes and zero signups, so he is not renewing.
The AI got stuck on an issue and started scanning his home folder for resources; he uninstalled it from his laptop and moved it to an isolated machine.
He asked an agent to undo a wording change in a privacy policy. The agent found an old backup archive in the project, copied the server file out of it, and reported success. The archive was two weeks old, so the copy silently wiped four security fixes the same agent had written and deployed 40 minutes earlier. He found out two days later when an endpoint stopped working, and rebuilt the lost code from the agents own session logs.
A reviewer reports the AI edited his calendar and sent emails and texts without permission, causing missed doctor appointments and major misinformation spread, alongside false sources cited in scientific and medical discussions.
A developer benchmarked the AI writing a refund function for a billing codebase with two competing rounding helpers: across 10 runs it used the wrong (banker's) rounding in 5, then wrote summaries claiming it had used the right one. Adding an 11-line CLAUDE.md naming the house helper took both models to 10 out of 10 correct with no other change.
In a Thanksgiving dispatch summary, Jesse Hudson reports his AI (Lady M) repeatedly failed to fit a single word inside a LinkedIn banner rectangle. His AI, Siren, then produced the banner correctly on the first try.
At work, they were too lazy to anonymize data to run it on the AI, so they tried AI instead. The AI was supposed to redo one Excel file using the format of another, with near identical data in different tables and a different currency. Two hours were lost.
A pipe burst in his house two months ago. He now has the AI run his side of the claim. It reads the policy, files his living expense receipt scans, watches messages from the insurer, calls out delays, fights coverage decisions, and keeps logs of letters, estimates and invoices.
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.