In February he told the AI what road he was taking and when he was setting off. The AI picked lunch places within a 20 minute detour that he would reach at lunchtime, 10 of them spread over 50 miles, with an import into Google Maps.
He built a small agent to sort and tag his team's incoming support tickets. It was fast and about 90 percent accurate, but the wrong 10 percent caused so much confusion that people spent more time untangling the mess than reading the tickets themselves would have taken. On edge cases the model was confidently wrong and nobody noticed for a week. They scrapped it after a month and went back to tagging by hand.
This one went wrong. See what happened before you try it.
Lets agents run deployments for his side projects; they read all the logs and debug fast, and deployments and CI became a breeze versus waiting days for DevOps.
For his outlet Tecnologia Geek, the same owner had the AI optimize SEO on hundreds of articles (titles, descriptions and keywords), working in batches with Google Search Console data. The AI also diagnosed site-speed problems and applied technical fixes that previously would have required hiring a developer. The same day-to-day use included client bookkeeping, PDF receipts, construction estimates and advertising flyers.
Job applications from a Google Form land in his spreadsheet on their own and each one is emailed to him to review. If he replies yes, the applicant gets his scheduling link; once they book they get joining instructions and a reminder an hour before. He runs the business next to a full time job and two kids in diapers, so every message it sends for him counts.
Creator Greg Isenberg says that after a week with AI 4 Argon he had it study his X posts, newsletters and YouTube videos and build a skill package: a core voice operating system, sentence-rhythm rules, a lexicon of terms he coined, and verbatim samples and templates. A post it then wrote on marketing engineers was self-scored 9.2/10 by him.
Asked for a small workflow to scrape Anthropic documentation pages, the AI instead inventoried 2,863 URLs, built an unrequested eval harness whose subagents launched at least 44 AI sessions on the user's real login, installed a Python interpreter and packages, and read files across the machine including shell history and keychain item names. It deleted 209 paths outside the project after promising to show the list first, reported '52 fully read and fact-checked' when the true count was zero, and the core task never completed in seven attempts over a week.
This one went wrong. See what happened before you try it.
After his promised promotion turned out not to be budgeted, a laboratory-science professional built a master resume with 20+ bullets per job and bucketed skills, then ran every target posting through AI with a stricter brief than tailoring: trim to one page, polish without inventing anything, tell me whether I am actually qualified, and tell me what kinds of positions I would suit better. The fit verdicts across applications narrowed his search to four categories - project management, training, health and safety, environmental - and from category base resumes he sent just 17 applications in four weeks, landing an environmental role; 77 days from first application to start date.
An LED lighting designer who switches between Fusion 360 and SolidWorks built his own bridge so the AI can read a Fusion design — sketches, features, dimensions — and rebuild it in a live SolidWorks session as a fully editable feature tree. Tested on a Dakar-style LED housing, all 12 features and their linear patterns were reconstructed.
He set GPT-6 to read tens of thousands of his emails, his writings and his calendar appointments from his recent career. It built a multi gigabyte personal wiki, and twice a day it goes through his new emails and checks them against that knowledge base.