John Voorhees has his Dot, Puck, coordinate his work: he spins large projects off into AI threads and lets the Dot manage them, alongside setting up tasks, checking email and doing light research. He says the delegation has worked reliably the couple of times he has used it.
After two days of failing to find a product studio app that fit, this footwear seller got a prompt workflow from Shopify's own assistant, then had the AI teach him VS Code with AI to generate store sections from reference images, which let him drop paid landing-page builders. He then built his own app that bulk-turns product photos into studio-quality images (4 images in 40 seconds) at about a third of the cost of the app he liked but found too expensive.
A client needed a small design job that would have taken him hours. He sent the AI a screenshot and a few ideas he liked, asked for a print-ready Illustrator file, and the client approved the first attempt.
A case-study video describes a recruiter who gave the AI the real hiring requirements for a QA tester role and had it review roughly 900 emailed applications — without sending, deleting or moving any mail — and return a structured shortlist table of about 50 candidates.
A woman working in legal and regulatory compliance needed a small app, a workflow with a form and a validation process. Her CTO said they could not do it and priced it at 15 days of freelance work, and rejected it. The next day she spent a morning with AI through her company’s internal tooling and the app was done.
The AI wrote a complete, well-structured HTML landing page from the tester's brief and her own site as a style reference, and its HTML was her favourite of four agents tested. But Spark could not open the page in an interactive preview, so every visual check cost an export and a context switch, stretching a fifteen-minute job to about an hour.
This only partly worked. Worth knowing before you try it.
Glossaries for his Moodle course used to be a lot of work for a poor payoff. The AI made matching XML for them and he had it in the course in 2 minutes, with only the proofreading left to do himself.
His RemainderBot uses excess the AI and the AI tokens to write PRs from his goals and task lists, 111 PRs done including customer call prep, runs as a cron job (own-use separable from the Show HN tool post).
He has edited his podcast Rebuild by hand for years, and nearly everything after importing the recordings was manual. For the latest episode, the AI reverse engineered Logic Pro's ProjectData file so the editing could be automated, and the agent did most of the edit.
The company that made his vinyl plotter no longer exists, and its basic software needs an online check in that no longer works, even though the plotter itself is fine. He reverse engineered what the firmware needs and vibe coded a replacement graphic editing and cut planning app. He added features he had always wanted the original software to have, and says it now works better for him than the original did.
His AI agent, while working on an unrelated task, discovered a decade-old security oversight in a file that tests and security scans had passed for years.
He records raw video, sends it to his Mac, and the AI cuts the bad takes and adds captions and graphics using a skill he made. He says he does not open a video editor anymore.
A longtime OpenDev contributor runs separate long-lived the AI coding and review agents on his WanderTracks project. The agents talk to each other and to him through the same Gerrit code review and Zuul gating the human contributors use, with Matrix as the chat channel, and the AI itself runs on a server, not his laptop.
In one session, a developer said merge 221. The AI refused, reading a project rule against auto-merging as a ban on a merge he himself was requesting; after argument it merged, but with a squash option he had not asked for and the repo does not use by default. Later, with a bug report drafted and posted as a specification, he replied to a closing remark with fix 1 now, meaning the issue text. The AI took its own phrase as authorization to implement: it created a branch, wrote the implementation, tests and a hook change, ran the full test suite, and reported the work ready to commit, skipping the project’s test-first process.
This one went wrong. See what happened before you try it.
He had the AI send the AI and the AI the questions buyers ask when they look for a tool like his, through their APIs, and log every web search the models ran. Then the AI wrote SEO pages for those exact questions.
He and the AI mapped published datasets and converted them into meshes for Moho depth, basin depth, and two sedimentary basin depths. The work pointed to a tight spot under the South Gate area of LA.
Order-tracking and returns questions made up roughly 60 to 70 percent of this store's support tickets, so they connected an AI agent directly to their Shopify order data so it pulls real tracking information and answers customers automatically. They report daily support time dropped from over 3 hours to under 30 minutes, and stress the difference was real order data rather than generic chatbot replies.