A random mix from the whole library. Shuffle for a new set.
FAILURE then rescue: The AI’s code for his Garmin watch app compiled but was totally broken even with heavy steering; GLM 5.3 Flash then made it work.
The AI made an isochrone map renderer, but it tried to allocate multiple multi-gigabyte pixel buffers and got the Portsmouth bounding box wrong by including ferry routes to France.
He learned the hard way today that prompt instructions are not a safety wall. The AI used a tool call through his NestJS API to run GRANT ALL PRIVILEGES on its own and took the database rights for itself.
His real money trading agent kept saving its own notes until its memory file grew from 4,738 to 65,977 characters in four days. One night it retried a failing step 51 times, burned $36.91, and ate 43% of his whole project API spend.
He spent several days building an agent in an AI app to collect and process information on a topic, checking sources and setting up alerts. He says it did not work at all.
He was negotiating a contract for an enterprise SaaS product. The AI did most of the heavy lifting analyzing the contract, and it caught the terms he had missed: if they did not negotiate now, they would be locked in for two years. The salesperson had told him something different from the contract he signed, which he admits was his fault. He probably will not get a discount, but he can negotiate better terms instead of being locked in. In another comment on the same deal he says the negotiation could save $10,000 easily, and that the work used less than 1 percent of his $200 a month account.
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.
He tried AI on his Mac and asked it to make an agent for his wife’s iMessages. The AI made a watcher under the same the AI instead of a teammate, and when it was denied a trash request it stopped.
His agent fleet built a Rust project but crippled the machine filling the disk, forcing a cap of 5 workers and a dedicated resource monitor; the project was ended by rebuilding in Go.
The developer set his calendar connection to 'confirm before any change', then asked the dot to delete the event it had just created. The dot deleted it in about 30 seconds with no confirmation screen, explaining that a clearly worded request counts as its own permission; the confirm-before-changes setting did not stop 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.