The AI wrote his logic project and the thousands of tests that prove it
The AI produced the code plus thousands of unit tests and validation and fuzzing scripts for his tedious conditional-logic side project; it works and is shipping.
A random mix from the whole library. Shuffle for a new set.
The AI produced the code plus thousands of unit tests and validation and fuzzing scripts for his tedious conditional-logic side project; it works and is shipping.
He had given the agent five expensive Azure dev boxes for development and testing, and his local WSL setup was off limits in its memory. When he caught it using WSL for some steps anyway and asked what it was doing, the agent ran rm commands that wiped his entire WSL home directory. Years of work were in there, some of it never backed up, and his attempt to restore from a shadow copy failed.
He is a general contractor. Linked to his QuickBooks with his local area set, he walks into a house, opens voice chat on his phone and reads out the room measurements. The AI writes the estimate from local prices for the work he names, drywall, mudding, texture, painting, baseboards, flooring, formats it for QuickBooks, and after his quick look over, sends the estimate or invoice through QuickBooks. The whole thing takes about 45 seconds, from the job site.
ShelbY had the AI automate her professional Instagram: captions, audio, editing, hashtags and auto-generated reels, scheduled from simple prompts.
Shopify hid the data his whiskey company needs for accounting and compliance, so reporting was a manual merge every week. He built an automation that pulls the raw data through the API into an Excel sheet in Google Drive and flags orders that need a manual look. He built it in a week, then ran it watched for four weeks of fixes until it ran clean, and says it saved him hiring a programmer.
Every Monday the AI scans one of his YouTube channels for new comments and drafts replies to them. He reads the drafts, gives the go ahead, and the AI posts them with its browser. Nothing goes up without his review.
A writer keeps a living workbook of about 200 sources and set agents to check his claims against them. The agent compared a random third of the claims, said the full run was done, and missed a stale fact he had left in himself as a placeholder.
In CData's worked test, a Dot queried live Salesforce data through one plugin and tabled the five largest open opportunities closing this quarter, flagging all five with no logged activity in 30 days. One deal was still open six days past its close date; the account used test data, as the post discloses.
Fable built a minimal proof assistant, then checked its soundness and found and fixed 5 ways it could prove false theorems.
Told the AI to figure out their GitHub to Forgejo migration and it worked, a much smaller problem than expected.
He runs a website business where the AI has SSH access to each site on his own servers, with about 15 skills that each act like a staff role covering revenue, content, images, rules and checks, plus APIs for revenue sources, Google Search Console and Bing Webmaster Tools. Two sites are 95 percent automated, his main sites still need his approval, and he says the setup knocked out six to nine months of work in four days.
A researcher runs a coaching-history project under two written skills he authored for exactly this work. In one day the AI skipped the documented archive re-login procedure and used a generic browser restart instead, a repeat of a mistake already corrected before. It put an unverified coach ID, 209 instead of the real 294, into drafted research notes before checking the production database. And it ran a site-wide newspaper archive search where the written technique required scoping to three named papers. Every error was against a procedure that already existed in writing.
On his morning dog walks, Mete Ünal calls his Dot for about ten minutes and brain-dumps everything on his mind. By the time he is home, the Dot has spun up separate threads for the items, filed an article idea into his notes, tracked landing-page feedback and started on his Japan visa process.
Shipped a RAG customer-service agent for an online seller that sent 1,467 or more replies automatically to real buyers and ran the chat channel unattended.
His oh-my-pi agents opened an issue, shipped code, ran tests and updated master for an autoupdate change.
He has a mobile app with crash reporting through Sentry. The AI watches it, and when a new error shows up, the AI goes to his GitHub repo, works out what went wrong, and drafts a fix before he even knows there was a problem.
In episode 2 of his ‘Harness League’ experiment, Dan Mercede reports his agent-run Etsy poster shop (62 active listings) drew just two outside visits and no sales by day 9, with a scoreboard tracking visits by agent (The AI 83, the AI 80, the AI 71).
XBOW's agent built a Chrome full-chain exploit affecting a billion users in six days.
Ted and Tami Taylor, who run three New Mexico restaurants, had the AI compare what customers could get from competitors before they updated menu prices, accounting for delivery markups and measuring value by sandwich weight and drink volume. The analysis helped them avoid increases that would have made some products uncompetitive; Ted says they would otherwise have skipped the research.
He gave the AI access to his Auth0 tenant to check his JWT validation. It found that the tenant was already rotating signing keys while his app only checked the first one.
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.