A random mix from the whole library. Shuffle for a new set.
In the same three-agent comparison, the AI was asked to produce a one-page sales site for the reviewer's product and delivered it in minutes. Presented as a chaptered test ('Test 2: a one-page sales site') in the Oct 17 video.
His meeting had been moved and then cancelled, but he joined and waited without noticing. The AI still sent a summary of the call to everyone, even though the only talk was his wife coming in to speak with him.
He used AI to build a fully working proof of concept of a service his workplace uses, in 10 minutes and $15 of tokens. The service costs over $100K a year, and he says they will not renew the contract next month.
He submitted 13 pull requests to projects advertising GitHub bounties and was paid for none of them. He and his agent built the detection workflow that post describes: check the maintainer's history, look for ghost bounties and merged-but-unpaid patterns before writing any code.
A creator who could not afford an editor paid for the AI Max and built his own post production studio, about 31,000 lines of code. Its smart cutting takes his raw filming and builds a DaVinci Resolve timeline for him, saving about 95% of the cutting time, and it also generates shorts and uploads with titles, descriptions, chapters and tags.
Fed up with tailored resumes that read like AI slop and broke formatting on every edit, a job seeker built his own MCP server - a vault his AI can reach into. Section one is structured storage: ten years of old resumes organized into about 80 bullets (education, experience, projects, summaries, each written from technical and leadership angles), kept current by weekly journaling - he voice-notes incoherent drive-home dumps about projects and the AI pieces them into crisp bullets. Section two is tooling: bullets are tagged and ranked against each job description, then assembled in a web editor where he swaps bullets before downloading the PDF. Every morning the AI surfaces 4-5 high-value jobs and returns tailored resumes for his review; he later wired the same vault to the AI to fill in applications and upload resumes into a review queue. Six months: 250 applications, 39 callbacks, 4 offers.
Caption+image creation scored 7.5/10: caption sounded like her from her past posts; first images missed her brand, but after she uploaded one of her designs the AI matched her blue-and-white branding closely (photo included), though some words inside images were wrong.
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 runs a freelance video editing studio and a coding studio, and his project folders were a mess across drives. He started a small folder making script with AI and kept adding to it daily for five months. It is now a 100,000 line Rust program with 1,390 tests that holds every project he has, gives each a permanent ID, and jumps him to any project on any drive or machine with one command.
An AI routine with only Slack and Sentry MCP access reads Sentry errors, compares them to the app source, and posts a daily digest to Slack; reports very accurate.
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.