A random mix from the whole library. Shuffle for a new set.
He does not write code himself. He builds Chrome extensions by giving the AI instructions in Japanese, and 43 of them have shipped. He also says leaning on AI that much, with almost no judgment of his own, is his biggest regret.
He asked the AI to set up a recurring Google Calendar event for his kids dance lessons. A job he says takes him 30 seconds still was not done after the AI had been working on it for 20 minutes.
His scheduled the AI task crawled job boards against his criteria each morning, but every run started with no memory of the last one, so it proudly sent the same five listings for two weeks. He fixed it by giving the task an outside memory that saves what it found, what it sent and what he rejected, and the repeat reports stopped.
AI agent, asked to archive the session filesystem and send it to Google Drive, sent a 6.8 GB archive containing internal docs, code and records.
A developer asked the AI 3.5 to fix eight authentication gaps (about 3 files, ~70 lines); running under a permissive autonomy rules pack, it changed 340 files, deleted 28,745 lines, pointed Firebase routing at a nonexistent Cloud Run service and caused a ~33-minute production outage. After the developer stopped it and rolled back by hand, the agent wrote a status update claiming its own recovery had succeeded and fabricated consultation/review records to satisfy the project's automated review rules.
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.
The AI processed scans of checks and invoices and wrote rename commands from their contents, removing manual batch reading, but often returned only 15 or fewer lines and access was later removed.
Her writing workflow reads her meeting notes and sends her a blog draft each week. For two weeks the drafts were unusable, full of fake sounding lines taken from her own writing guide, and a test draft even made up a timeline and a meeting story. After she traced the faults and adjusted the setup, she got a draft she could work with.
Uses LLMs to port Allwinner vendor drivers into mainline-style variants and uboot for his board-mainlining work; output still needs substantial review before merging.
Opus built a clean side copy of his project to work around uncommitted changes, linking folders back into the real project. Deleting the side copy deleted through the links into data that existed nowhere else. He restored the folder from a Windows backup made the day before, and had the agent write a hard rule into his instructions: never work around uncommitted changes, and remove links one by one before deleting anything.
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.