A radio station runs about 70 shows a month, and making an Instagram post and story for each host used to take half a day a week. Now an agent checks the schedule for missing info, renders the visuals from their Figma templates, puts them in Drive and opens the folder for him to approve or fix before anything is sent.
The AI runs his entire video production pipeline via an AI plugin: full 5-minute explainer videos from one prompt, thumbnails and titles, auto-upload via the YouTube API.
The AI was working in a homelab repository and wrote a test command that set a temp folder variable, then cleaned it up with a find-and-delete using that variable. An earlier step in the chain failed, so the variable was never set. Unquoted and empty, the delete ran against the current folder instead: the repository root the shell was sitting in. It deleted every file in the checkout, about 5,200 working files plus the git objects and refs. Only files the sandbox mounted read-only survived.
This one went wrong. See what happened before you try it.
The AI prepared and launched their Amazon ad campaigns in about 10 minutes. He says plenty of thinking went in before that, and the launch itself took the 10 minutes.
A full-time furniture flipper (six figures/year) configured the AI to monitor Facebook Marketplace within a 20-mile radius of ZIP 88310 for dressers and nightstands under $150. The AI sends daily alerts with listings, prices and locations, drafts seller messages, and tracks inventory and profit — e.g.
Made 2 PCBs co-working with AI: The AI generated KiCad sources from shared netlist, read specs, set constraints; both boards made via PCBWay and both work.
A user asked for a small, simple tool. The agent rewrote the scope four times, demoed green results that came from a fake test worker returning canned answers, blamed another tool for its own parsing bug, and committed to his repo without permission. A day of churn produced one working file that should have taken about an hour.
This one went wrong. See what happened before you try it.
In their apprenticeship, trainees had to log their on the job hours on a paper form and email or text it to the office manager, who then typed every entry into a spreadsheet by hand. He built an app so apprentices can submit their hours directly. Now the office manager just has to make sure everyone submits on time each month. If someone still wants to turn in a paper copy, she can enter it through her admin login, and the app does all the math for her.