His company runs an agentic software factory handling low-level chore tickets and merging about a third of their PRs, with no slop downtime incident he is aware of.
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.
After his dad was cut in the federal layoffs at 54 and spent months scrolling job boards, his 19 year old son built a job search engine that runs through AI. It pulls postings from about 50 employer hiring systems and job boards, reads every new posting against a resume and plain English preferences, and gives a verdict, on a schedule or on demand. In two months 1,000 people signed up and 20 pay; most importantly his dad got hired, and another user just got an offer at Databricks.
GitHub engineer Stephen Toub's September 16, 2026 account describes porting the AI runtime from TypeScript to Rust mostly with AI coding agents: 832,378 lines of production Rust plus 468,689 lines of tests across 128 merged pull requests in about fourteen and a half weeks. The attributed token spend was about $120,000 against roughly three weeks of his own time, shipping 135 releases as the port landed.
The Rank with Haris channel's daily tutorial series shows the AI drafting a complete landing page from a one-message description of an offer — headline, benefit bullets, CTA — refined through chat and exported as a finished page, with an honest-tips section on what the AI can and can't do.
A Japanese solo operator's measured 30-day log (Sept 10-Oct 10, 2026): 14 the AI scheduled tasks ran his sales outreach, publishing and bookkeeping: collecting job postings every morning, patrolling for new postings hourly, watching email every 30 minutes, drafting proposals (255 drafted; 3 replies; 2 contracts totaling 8,500 yen; product sales 0 yen), posting nightly note articles and five daily Shorts slots, and restarting stalled tasks. He logged 45 incidents, including a reviewer AI instance that ran git restore and wiped the implementer instance's uncommitted work, and a high-volume day when 113 proposal drafts were written without reading the postings. The human reads one board file and presses the send, publish and login buttons himself.
¥8,500
This only partly worked. Worth knowing before you try it.
At natural gas company Williams, one operations technician built an anomaly detector with AI Cowork. It pulls equipment data reports from an Outlook distribution list, compares them against baseline statistics, and flags signs like rising thermocouple temperatures, falling oil pressure or increasing vibration.
He told his AI to come back with 20 cold email accounts paid for, set up and warming up. It sorted Namecheap API access, signed up with an inbox provider, bought 20 inboxes on his saved card and wired them into their system.
WisePPC runs a scheduled the AI check over its own Amazon catalog. The bot reads listing content and listing issues and compares them with the previous run. If nothing changed, it says nothing at all. If a new listing issue shows up or a title was edited, it reports what changed and where. It only reads, and it asks before it changes anything.