The AI made the change I asked for and broke the whole program
He used AI to mod a program he uses. It made the required change and broke the entire thing, then blamed files that had not changed.
A random mix from the whole library. Shuffle for a new set.
He used AI to mod a program he uses. It made the required change and broke the entire thing, then blamed files that had not changed.
He follows the CNN lawsuit over White House press briefing access. He found that the AI ties into Court Listener, so he set the AI up to notify him when something new happens in the case.
Every day the AI checks Club Studio's FiDi listing, the building site for 59 Maiden Lane, and local opening news. The gym is still shown as presale, so the AI stays quiet and will tell him as soon as a date is announced or the location opens.
He added a weekly ops review to his AI chief of staff bot. Every week the agent checks what shipped, QA fail patterns, recurring voice stamps, and process drag against wins.
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.
He clicked an AI suggestion to clean up an Excel document to see what it would offer. Excel crashed at once, and his unsaved documents could not be recovered.
Gail Moody (1.8K followers) ran a head-to-head trial of two AI assistants. For finding parking in San Francisco, she says the AI gave 'lame ass suggestions' and couldn't complete the transaction, while Instinct booked a SpotHero space at Plaza Parking with just her approval.
A session generated a Word document with a script. The user then edited the document in Word for about 40 minutes and saved. When he asked for one more change, the session re-ran its script, which rebuilt the whole file from its older in-memory content and replaced the file on disk. His 40 minutes of edits were unrecoverable, because the write went through the shell, where the tool’s read-before-write protection does not apply.
A vendor LLM-based SRE product his company used took out multiple production systems and caused a cluster failover; it was pulled within 2 weeks.
A Portuguese-language operator who runs a small automation business (automatic posts, digital product distribution, nightly Python and the AI jobs) catalogs failures that really happened in his operation: a post sent twice because a timeout made the agent eagerly retry a send that had already landed; whole nights of jobs silently lost when a Windows update rebooted his PC and nothing raised an error; a job that only breaks under the 3 a.m. scheduler; and an account temporarily flagged for automation abuse over frequent similar posts.
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.