A Korean solo developer's two-day diary of putting the AI to work as his team: GitHub issue labels split between him and the AI across marketing, planning, design, QA, operations and finance, with a project board and roadmap milestones built in about an hour; the AI runs QA on each deploy event and files issues; customer inquiries are answered through an admin MCP connection; and morning routines from a one-time setup (7 AM English lesson, Google Analytics analysis, issue briefing) arrive unprompted. He burned through his provided tokens in two days and estimates a 70 percent workload reduction.
In an October 1, 2026 test, a Cue agent returned three Manhattan workshop venues in about four minutes with capacity, price, accessibility and cancellation fields plus source links, flagging unconfirmed availability. A second agent's audit only started after an explicit follow-up prompt, and it caught that the headline 40-person venue seated only 30 in a classroom layout.
This only partly worked. Worth knowing before you try it.
He built a setup that links the AI with Photoshop to handle a work task that is too fiddly to call simple. When a request came in from a client, the setup did the work and he delivered it so fast the client said they had expected it to take about 2 weeks.
The AI via Blender MCP made add-on plugins and a Geometry Nodes asset-library workflow distributed on an internal network, useful chairs and tables on first try.
Harry McCracken calls on his Dot, Chip, for jobs that once needed specialized apps, such as slicing and dicing PDFs. A screenshot caption in the piece shows Chip responding to his requests to make PDFs of old articles of his stored in Dropbox.
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.
This one went wrong. See what happened before you try it.
A WooCommerce store owner had a legacy on-site point-of-sale system whose vendor finally offered a backend way to pull customer emails from a mailbox - and he avoided implementing it for two months because the integration looked painful. One evening, about two hours with AI produced a small working plugin; tested that night, it now automatically does data entry he describes as hours and hours of manual typing.
The AI saw that Caddy was nearly out of memory on his service, checked the traffic, and found bots hitting IP addresses his customers never use. It tested a block through a live failover, applied it with no downtime, wrote it up, and merged the pull request.