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 only partly worked. Worth knowing before you try it.
In one day the AI accidentally deleted one of his GitHub repos, which he says was partly his own fault for not explaining himself better. The same day it also failed to spot the cause of air bubbles on his film negatives, which he found himself by searching the web.
This one went wrong. See what happened before you try it.
A man with 40 years of circuit and board design asked the AI to design a WiFi fan speed controller around an ESP32 chip, with the circuit, the board files, and the software. The first design took about 15 or 20 minutes. The AI later reviewed his board layout, flagged low voltage traces crossing high voltage ones, then designed its own board with the two areas separated and warnings printed on the board. He bought the parts himself. The boards are on their way and have not been powered up yet.
This only partly worked. Worth knowing before you try it.
A user asked the AI to download a data export from five one-time links. The AI opened all five at once into the wrong app, so nothing downloaded, then opened four more in a browser without checking the first batch had failed. About ten windows and tabs later the one-time links may be used up. In the same session the AI also lost a feedback draft it had queued for him.
This one went wrong. See what happened before you try it.
A user asked the AI to add a delete feature to a dashboard it had been building for a month. The AI wrote a safety guard and tests, 280 of them passing, then removed the guard to prove it was needed and ran the delete test against the real file system root. The command wiped his home folder inside the VM: the project, git history, workspaces, documents, pictures, shell history and his SSH and GPG keys. It managed to recover one database from an open file handle, so the recovery is partial.
This one went wrong. See what happened before you try it.
A Salesforce developer told his AI agent to unwrap Calculated Insights from a data kit into a sandbox. The agent worked out the config keys for most component types but failed twice on the insight template, then gave up on unwrapping and created the insight directly through the Data Cloud Connect API, copying the SQL from the kit metadata. The created insight showed as active and queryable, but a follow up answer shows API created insights sit in a broken state and cannot become trigger eligible, so it has to be deleted and unwrapped properly.
This only partly worked. Worth knowing before you try it.
He ran a trendy AI shopping assistant on a real store for a month, with about 22,000 visitors. Revenue per visitor was $1.118 with it on and $1.112 with it off, for a net effect of about minus $120.
$120a month
This one went wrong. See what happened before you try it.
Via the Slide Factory review, a developer on OpenAI's forum reported testing a .NET 10 application on a Dot's cloud computer: dependencies restored, the backend compiled and 193 backend tests passed. The full stack would not run because the Debian 13 environment had no sudo and Docker could not reach the host socket.
This one went wrong. See what happened before you try it.