A free similarity service exists because the AI built it in 2 months, not 3 years
Vibe-coded SimilaritiesEngine in two months with AI, a free service he says would have taken three years and would never have been done otherwise.
A random mix from the whole library. Shuffle for a new set.
Vibe-coded SimilaritiesEngine in two months with AI, a free service he says would have taken three years and would never have been done otherwise.
He asked the AI to tidy his todo inbox in milieu.cloud. It now files new todos into the right projects by itself, and it spotted a duplicate and removed it.
During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.
A video summary was made for others to use in their teaching. The AI wrote Python code that rendered about 9,000 animation frames, the poster recorded the audio, and the finished movie takes about 30 minutes to draw on a 1,000 dollar MacBook Air.
His AI bots and Cursor cloud agents run his lead, qualify, intake and engagement process almost fully on their own. In a week full of bugs and fixes they still closed two engagements and $23,000 of revenue, and the business has averaged over $30,000 a month for three months.
A consultant runs 21 the AI jobs, all switched on. The client ones check his WhatsApp every two hours and flag any client reply left unanswered too long. Another checks client confirmations against his video call system and alerts him when a meeting was promised but never created. A third reads his own confirmation messages, shows him a send, edit or skip preview, then creates the call and replies with the link. Draft replies are prepared the same way and only go out after his tap.
Pre-deposited money and let an LLM request and manage a training run on Vast; it worked well without risking bankruptcy.
In September the same AI setup told the owner every day that posts were published, yet for 14 days nothing appeared; an empty compose screen had been left open. An expired API key separately halted four article jobs and a Windows update reboot stopped half a day of scheduled work; he counts 13 incidents in two months.
A Builder.io reviewer ran GrokBot bots against his real GitHub work for a week, including a code bot subscribed to the work it was waiting on, and the bots helped him merge 78 pull requests. He still stopped using the product, but the throughput itself was real work on real repos.
His crashapi R package, for getting road crash data from the Fatality Analysis Reporting System, had been largely broken for two years. He used AI to bring it back, and the package is live again.
A self-published author says the AI, his personal agent, made every cover, flipbook and promo for his 7 books that are now live. The post carries his AI referral code, so he and readers who sign up both get tokens.
He points an AI project at a folder of case files. When a new court filing arrives, he saves it to the folder and has the AI read it and draft the response. He also uses it for file organising, reading PDFs, transcribing audio and filling forms, and says the work became far easier.
Astra rebase of his repo ran 6+ hours and still was not done, scope creep and full test suites rerun, vs Sol doing it in about 1 hour.
Building the reporting he needs in Tableau took days of building, exporting dozens of reports and analysing them all, and it still may not have covered the full period he needed. With an AI connector, the same job was done in 10 minutes.
The AI and the AI ran an entire short-video pipeline from script and narration to images, animation, edit, QA and upload, with the author only reviewing.
A Low Code Studio creator gave the AI a single prompt describing a Compliance Tracker app; the AI designed the data structure, created the SharePoint list with columns and data types, and wrote the YAML for all four screens. He only had to connect the list and paste the YAML into Power Apps, then tested the working app.
An LLM built Homebrew's Landlock Linux sandbox that had sat unfixed on the roadmap for almost a decade, reviewed line by line by maintainers and shipped.
Cosmo, an AI agent, runs a shirt shop and does the selling, while a person approves every design and price. Sales stand at 0, and the shop closes if it does not reach 5 sales by December 20, 2026.
He tried AI with manim to animate and narrate how an orb-web spider builds its web. The finished video is on his YouTube channel.
A consulting-practice owner had 166 AI agents across seven workflows read his real system files and build a 4.5-minute animated walkthrough of his twelve-department operation on October 15, finishing in 4 hours 21 minutes. Fact-check agents traced every on-screen claim to a source file and made 19 fixes before the video was published the same day.
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.