A random mix from the whole library. Shuffle for a new set.
Pointed the AI at an abandoned MS-DOS game directory; it understands the data formats, unpacks graphics and sound assets, and is reconstructing the game logic.
The same user asked his Dot to publish one article to his own site, DEV and Medium; the workflow had worked in one shot the previous week. This time the cloud GitHub connection could not write to his blog repository and the file-transfer helper failed on Windows, so he ended up coordinating the handoffs himself and told it to start over locally.
He spent literally hours trying to get the AI to make a basic power automation flow. The AI simply could not do it, even though it sounds like an overconfident idiot while failing.
Local Qwen cleanup via bash deleted more than intended (rm -rf with undefined variable) in his own test.
Four ways his unattended agents reported success while doing nothing.
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.
Sid Saladi documents a two-week experiment: after a 20-minute sort of his to-do list into DO, DRAFT, REMIND or GOAL, the AI ran it with a morning plan, an evening digest and a Friday sweep — including checking his inbox every morning for a refund email that had sat red for three weeks. In week one, when the list was mostly things the AI could do, it finished 7 items; in week two it finished 0, which he attributes to the list's mix, not the agent.
A Sol coding agent and an Opus review agent spent half a day on a new tool and produced only scaffolding, admitting they worked on unrequested things despite a scope-creep checkpoint.
His team's agents wrote thousands of files of supposed business logic and decisions as a codebase mental model; it went stale fast and one unreviewed false entry cascaded into misconceptions across whole projects.
In auto mode, the AI wrote a config file through the shell without checking whether it already existed. The file, staticwebapp.config.json, already existed and held the security rules for his site. The overwrite wiped them completely. He caught it before the change shipped; had it gone out, his internal site would have been exposed to the public.
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.