The AI moved his product's database over a weekend; months later he is still happy
Migrated his product from DynamoDB to Postgres over a weekend with AI and has been happy with the change 4 to 6 months later.
A random mix from the whole library. Shuffle for a new set.
Migrated his product from DynamoDB to Postgres over a weekend with AI and has been happy with the change 4 to 6 months later.
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.
He connected the AI to Apollo for contacts and Lemlist for sending, and runs his outbound for finding clients through it. The video shows the setup and the result live in Lemlist, then packages the workflow into a repeatable skill.
The AI wrote a test run scheduler and migrated to nextest, cutting local release build cycles from 60+ seconds to about 3 seconds.
Asked the AI to break his team's own Postgres MCP guards and it found pg_logical_emit_message, which writes to the WAL inside a read-only transaction, leading to a hardened replacement.
A SimplePost user hit an error while the owner was on vacation with his family. The AI checked the logs, found the issue, fixed it, and drafted the explanation email in Gmail, and the owner reviewed and approved each step.
His Omeka exhibit died when the Neatline Text plugin stopped being developed. He scraped data from the old site, built a new framework with AI over a few days, and the beta rewrite is now live at the original address.
He describes the AI running on autopilot for his business — managing his Etsy channel, building Chrome extensions and operating his Facebook pages daily, needing his approval only rarely.
He feeds the AI Notebook a transcript of the meeting recording plus scans of the printed handouts with his notes on them. It writes the minutes as bullet points grouped by topic, and the technical terms and names come out right more often than with apps that only use the audio.
He runs his own small businesses with AI agents. Each job has its own agent with its own instructions file: one triages the inbox, one handles outreach, one prepares quotes. The agents only draft; he approves every email and quote from his phone before it goes out. A brief arrives at a fixed time every morning with the overnight replies, what is waiting on him, and the follow-ups for the day, and it replaced his own daily check-in. When he corrects something, the correction goes into a shared notes file that every agent reads, so he only has to say it once.
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.