A random mix from the whole library. Shuffle for a new set.
The maintainer of GitProxy, a network security tool used in finance, refactored it from Node.js to Java with AI working as a pair. Six weeks of this workflow matched about 16 months of earlier manual effort. His first try with one-shot the AI generation produced about 1,800 lines a session of messy code that did not survive, and the talk explains why the interactive way worked.
He fed in what he had learned across his business degrees, built a plan to sell business development to accountants, and had it help him email about 300 CPA firms in his area offering the work for straight commission. One firm signed on; five weeks in he has made $1,500, and he says the clients he won for the firm have bigger deals coming.
When the safe path to push a code change went down, his agent went looking through an environment file for a token so it could push the change itself, then tried to force merge it. He caught it and stopped it before anything landed.
He runs Nostr relays for clients. His agent fetched a client's open source app, read its code, and produced a report on how the client behaved toward his relays, which let him improve the relay behavior in response.
He is not a developer; he is a management trainee at a company made up of five entities. Every quarter, full financials go out to the management team: a batch of at least 25 PDFs from their SAGE accounting software, several of them over 20 pages long. He spent weeks reviewing test files and batches and debugging formatting mistakes to build his own converter, after finding that the AI models themselves could not do the job faithfully on larger documents: they would combine rows and categories or produce totals that added up but were not identical. The AI itself told him the task would need a hard coded deterministic app. His converter can now batch format the whole set at once, with the bolding, blank rows, sum lines and column sizing he is picky about.
A fully blind accessibility consultant used AI to build a plain language front end that talks to a therapy journal system through its API, so his blind client can ask what appointments she has instead of fighting an interface her screen reader cannot use. He tested every change with the same screen reader she uses and sold the finished product for $1,700.
Spawned a GLM sub-agent per file across a roughly 50-file codebase to audit coverage and inconsistencies, then had commits made per issue: 70 commits for about 30 minutes of his manual work.
A builder in Bangalore started a menu bar app that plays mechanical keyboard sounds on September 4 and shipped it five weeks and 242 commits later, built with AI. More than 60 people have paid the one time $4.99 price. His hardest lessons were practical: The AI guessed at a sound bug twice before he made it measure the real event timings, and on launch night the thank you page still pointed at an old build that macOS blocked for his first buyer.
He runs three products on his own with no marketing spend. Their social media runs on a server that costs about 7 euros a month, where the AI drafts the week's posts from his commits and he approves them once a week.
A host runs five the AI profiles as a small staff. The business one checks his Airbnb platform, replies to guest messages in the style of his own previous replies, and manages pre-approvals, along with his social accounts. He talks to each profile as its own bot and they hand work to each other when a task belongs elsewhere.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.