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.
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.