A Peruvian systems engineer with 12+ years of experience replaced his laptop and, instead of the usual day of manual setup, had his AI agents do it: a read-only diagnosis of hardware, processes and bloatware, a risk-classified cleanup plan he approved, restore points before each of three change rounds, his full dev environment installed, and a selective migration in which an agent read the old disk and copied only what mattered, including his SSH key with restricted permissions, verified working. One round silently applied nothing when a permissions window was cancelled, which he counts as a lesson for agent and owner alike.
This only partly worked. Worth knowing before you try it.
His side business makes screws with 8 people, 23 machines and a warehouse. Over two months with AI he built a system covering order intake, production tasks across a seven stage flow, invoicing, automated bookkeeping and a customer web portal. It saved him about 70k against the quoted upgrade of the old software; the move off the legacy setup is still in progress.
This only partly worked. Worth knowing before you try it.
Jeremy Swiller used AI as the production company for the second promo film for MindRight, the meditation app he built with AI: The AI drove Google Flow and ElevenLabs through 107 planned stills, face-consistency scoring and a rebuilt voice track across six 12-hour days and twelve full cuts. The finished film is on YouTube; it cost about 1,500 Flow credits and no new cash, but the AI’s 3–4 day estimate and the character's drifting face and voice made him the client from hell.
This only partly worked. Worth knowing before you try it.
He set up saved searches on Cars.com, Carvana and CarMax with his makes, models, price, year and features, and favorited cars on each. The AI merged them into one list, checked price guidance, mileage, consumer reports, recalls and reliability, named his ten best and ten worst, and removed the bottom ten from his favorites. They repeated the rounds until the list was tight, then refined by color and features. He test drove two cars from the list. While he was out, the AI checked the stock of two dealerships he drove past, just from him naming the brands nearby, and found one more match. Every morning it reruns the searches, removing cars that sold and adding new ones.
This only partly worked. Worth knowing before you try it.
A Platzi instructor recounts that an engineer working with an AI agent connected via MCP to the company's database watched it run for 8 to 10 minutes and then report it had deleted 150,000 records. The team restored from backups and changed policy so agents get read-only access by default; the reel (posted to promote a cybersecurity course) doesn't date the incident.
This one went wrong. See what happened before you try it.
He asked the AI to deploy his product site. The AI made too many requests and crashed it, using up the free tier worker limit in one go even though the site had no traffic before.
This one went wrong. See what happened before you try it.
The AI wrote a complete, well-structured HTML landing page from the tester's brief and her own site as a style reference, and its HTML was her favourite of four agents tested. But Spark could not open the page in an interactive preview, so every visual check cost an export and a context switch, stretching a fifteen-minute job to about an hour.
This only partly worked. Worth knowing before you try it.
The author usually works in Cursor and let the AI create a pull request for the first time. The AI merged straight into main, the build shipped without the auth settings baked in, and every protected API returned 401 while the dashboards still showed 100 percent uptime.
This one went wrong. See what happened before you try it.
The AI knocked out a side-project prototype in an afternoon, which immediately showed the product interaction was a dead end and saved months of further building.
This only partly worked. Worth knowing before you try it.