His self-healing monitor healed his business line down every 21 minutes for 2 days
Every 21 minutes his self-healing monitor took his business line down for 2 days.
A random mix from the whole library. Shuffle for a new set.
Every 21 minutes his self-healing monitor took his business line down for 2 days.
On his boss’s suggestion he tried AI to compare two documents. It failed badly, and about 15 minutes later he was back at square one.
Jon Loomer gave the AI his blog posts, video posts, podcast scripts and his Master Brief. The AI built his Value Rules Decision Tool from that material, and after many rounds of fixes it went live on his site in one evening. He wrote no code.
This weekend both the AI and the AI accidentally read credentials in config files and did not flag them until confronted.
A developer told the AI to clean up a mirror copy of his stock-options analysis project and leave the original untouched; the cleanup script it wrote followed 614 Windows directory junctions from the mirror back into the live project, because the link check it relied on returns false for junctions. In 103 seconds it deleted 48,218 live files and emptied the .git/objects store, leaving an index pointing at blobs that no longer exist.
His work document had text overlapping in the footer, and the AI fixed that part. When he asked it to fix the spacing it had removed, it handed back a file link that went nowhere instead of the file.
Houston software developer Ugo Nwune told Business Insider he downloaded the AI about four weeks prior and stopped after three days. He had granted only Facebook, Threads, and Instagram access.
He used AI and the AI to build a setup that automatically made one LINE sticker a day. He stopped the setup once he was happy just having built it, and the stickers stay on sale in the LINE Store.
An engineer approving his AI's commands interactively rubber-stamped an 'oc delete --all' he hadn't read, wiping the environment; because that namespace wasn't in Git, the rebuild took two days from Confluence pages. Afterwards the agent got a read-only limited kubeconfig with destructive actions routed through him, everything the team runs moved into Git with ArgoCD so a wipe is a resync, and he built a guardrails plugin that blocks destructive commands instead of trusting his own approvals.
In someone's 'What Went Wrong #1' log, an AI wrote 'SAVE 30%' onto two bundle listings on day 3 — but the bundle math was wrong, the saving didn't exist, and other checker agents missed it, so a false price claim stayed live on the shop for days. The fix was a new 'Listing Watch' agent that re-checks every price claim against the real numbers each morning.
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.