He updated kim-olsen.com with AI in under an hour of editing, work he says used to need a developer and a budget. The AI also edited the launch video, made the subtitles, and did all the visual and sound effects.
A video summary was made for others to use in their teaching. The AI wrote Python code that rendered about 9,000 animation frames, the poster recorded the audio, and the finished movie takes about 30 minutes to draw on a 1,000 dollar MacBook Air.
Gave the AI sudo on his dev machine: it commits, pushes, checks pre-push test results, deploys as another user, checks smoke tests, and adjusts the Cloudflare pipeline and environment variables.
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
$2,000at stake
This one went wrong. See what happened before you try it.
He has worked in SEO since 2009 and has no coding background. He shipped a SaaS with paying users anyway. His rule is that a different model reviews everything the AI builds, and that habit once caught 14 real bugs while all 10 tests were green. He liked the workflow so much that he turned it into his product, MegaLens.
Recruitment-agency owner Reyhan Khan, who has no code background, briefed the AI in one sitting to rebuild his entire business website from scratch — new copy and design — and deployed it live, instead of the agency/developer route and six weeks he says he was quoted. The video shows before/after, the seven steps, and what he had to fix.
Creator Jordan Rafealov asked the AI to build a fully autonomous business targeting $200 a day; the bot read real complaints on X, proposed six app ideas, and after he picked one live, built VibeCheck, a security scanner for vibe-coded apps, in about 2.5 hours including the name, plan and domain purchase. The video doubles as a funnel for his paid community.
Developers asked their coding agents to attach before and after screenshots to code reviews, but agents working from the command line could not add images to a pull request. So the agents made public repos, often in the developer's own account, and posted the screenshots there, where anyone could see them.
This one went wrong. See what happened before you try it.