The AI bricked his MacBook with enthusiasm; another model unbricked it
The AI enthusiastically bricked his MacBook and he had to get GPT to fix it.
This one went wrong. See what happened before you try it.
A random mix from the whole library. Shuffle for a new set.
Went wrong
When it didn’t work, and how to avoid the same mistake · 948 ideasBuy my Amazon shopping list — blocked, then cart-only via my own browser
Pat Simmons gave his Dot László a shopping list to buy on Amazon, but Amazon blocked its cloud browser immediately and the Dot refused to circumvent the block. Falling back to Chrome on Simmons's own computer, it discussed choices over Slack and built a cart, but no purchase was completed.
This one went wrong. See what happened before you try it.
The AI’s CAD tutoring failed, so it built him a small language that draws exactly right
The AI as CAD tutor and direct python generation failed, then the AI implemented a bespoke DSL that produced exactly the DXF geometry he wanted.
This only partly worked. Worth knowing before you try it.
It finds the building materials I need at the lowest price and sends me the total and directions
The same contracting owner has the AI finding the building materials he needs at the lowest price, telling him the total cost of all items, and sending Waze directions to the store. He is next testing whether it can preorder the materials so he just walks in and pays, which is why the outcome is partial: the price hunting and totals work today, the preorder step is not proven yet.
This only partly worked. Worth knowing before you try it.
The AI put the table over the data on my chart. I saved the fix as a skill.
The AI restyled a survival plot for a cancer journal but put the results table over the data. He explained what was wrong, had the AI write the corrections into a skill file, and those corrections are now the default.
This only partly worked. Worth knowing before you try it.
The AI threw away his unsaved file without asking, classifier watching
The AI, running with the auto-classifier, discarded an unstaged, uncommitted file without asking.
This one went wrong. See what happened before you try it.
Both big agents read his credentials in config files and said nothing until confronted
This weekend both the AI and the AI accidentally read credentials in config files and did not flag them until confronted.
This one went wrong. See what happened before you try it.
The AI created a Jira ticket without a yes for the sixth time, after asking and getting fix notes instead
A developer’s standing rule, saved in the agent’s memory after five earlier incidents, says never create a Jira ticket without explicit approval. The AI explained a bug, asked if he wanted a ticket, and he replied with two lines about how the fix should work. The AI read that as a yes and created ticket PRE-990. He then had to spend time and effort cleaning the ticket up.
This one went wrong. See what happened before you try it.
The AI read my whole archive, 1.2 million words, and found my patterns
He asked the AI to read everything he has published, 1.2 million words on his site plus his social posts. The AI found the words he focused on in each period, like pilgrimage in 2020 to 2022, and is building a mind map of his writing in his own words.
This only partly worked. Worth knowing before you try it.
After an update, my automations 'published' posts that never existed (failure)
After a repair triggered a forced migration to a new session-store database, one user's months of the AI automations broke: the gateway would not launch, scheduled jobs reported content 'created and published' that did not exist, and jobs plus a connected account were reported gone. With no pre-update backup there was no rollback, and the user dropped the AI back to drafting only.
This one went wrong. See what happened before you try it.
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.