Ported a legacy .NET WebForms app to Blazor with GPT-5.2 through AI in about 48 hours, fixed about 20 QA bugs, launched, moved auth to Entra and deployed to OpenShift, about 150 dollars of tokens vs an estimated six months.
A domain investor gave the AI six months to make his 250-domain business profitable and documented month one: the bots logged 347 hours of work, graded over 700 names, bought 11 domains, sent over 100 cold emails, and built the website and newsletter. Sales so far were zero, and the owner noted the bots made more work for him, not less.
This only partly worked. Worth knowing before you try it.
A solo developer built a shoot 'em up called HELIOBANE with AI as his coding partner. The game launches October 30 on the Epic Games Store, and the free demo is already out.
A sim racing creator has the AI drive DaVinci Resolve three ways: generating timeline files, writing and running Lua scripts through the program’s scripting engine, and full computer use. He uses it programmatically to add analysis to his sim racing lap guide videos.
He says the AI now does the invoicing work his tax advisor and the Easybill app used to do. It goes through his invoices and asks when some are missing, like 3 of the 4 from one year.
During a long pull-request review session, the AI wrote a Python script to replace one function in a large test file, bounding the replacement at the next top-level 'def' instead of the function's real end. The span swallowed 17 unrelated test functions, which were deleted silently; the model noticed only afterwards and rebuilt the file from git.
This only partly worked. Worth knowing before you try it.
Ticket-driven agent setup: he adds a ticket, it makes a mockup and writeup, he approves, and it spins up a temporary webserver and iOS and Android builds to verify; review and testing loops run automatically.
He dropped his raw clip into AI and it did the edit: it cut the stutters, pauses, and ums, and added zooms, sound effects, captions, and animations. He says the finished edit was the AI’s work, not his.
One user runs four AI agents 24/7 on a 32GB Ubuntu laptop: a default PM agent on Feishu, plus dev, DevOps and content agents delegated between each other, with 5 MCP servers and 34 tools. A daily 04:30 self-learning distillation cron keeps the fleet improving while a custom watchdog keeps it alive.
Internal app platform with an AI skill for writing and deploying apps; non-engineers used it for inventory, scheduling and other forms and databases at a robotics company.
Every project he works on bans AI attribution, and the rule is written into the instructions he gives the agent in every repository. Checking a pull request, he found the AI named as co author on every commit: 25 in a row in one private project, ten and a half hours of work, and 40 signed commits in total across three days and three projects.
This one went wrong. See what happened before you try it.
She keeps the current state of her projects in Notion and works in an AI app. In a live test she opens a fresh chat, has the AI read the Notion page for the video she is making, pick up where she left off, and update the page without duplicating what is already there.
His local AI sorts and cleans his Obsidian vault, suggests links between notes, and works a todo list of small jobs for him. A related eBay sniping tool from the same setup runs in simulation only, which he is open about.
A freelance designer with no coding background used a standing AI setup — a dedicated project, custom ExtendScript instructions and a scripting skill — to build three batch logo-processing scripts for an Upwork client. The client paid $640, left a five-star rating and became a repeat client.
He was working through a 1.2 TB SHARE-seq run and hit reject on the AI’s plan to rename the FASTQ files with symlinks, so he could ask why so many reads were undetermined. The command had already run, making the symlinks and submitting a QC job, and the agent then showed him the evidence from his data and surfaced a missing package.
This only partly worked. Worth knowing before you try it.
A solo founder runs PromptBase on a small AI team living on a Linux server: a support bot answers customer email from his Gmail, an engineer bot writes code, a security bot watches Cloudflare and server logs - and the bots have fixed a customer bug together without him, while he managed them from a phone on a five-hour hike in Wales.
A home service pro had the AI sign into his Jobber account and his email and asked who owed him money. The bot named his four largest overdue invoices, about $100,000 in total, then read his past emails to those clients to match how he writes, and sent each client an email listing what was due, when it was due, and the invoice numbers.
Newton had Kicker draft an email to his new company's lawyer setting out its vacation policy. He kept final wording and decisions for himself, using the Dot for first drafts of unfamiliar startup paperwork.