Last week I published a change to this website from my phone. Not “sent myself a reminder to do it later” — published it. Wrote the change, reviewed it, approved it, and watched it go live, all between two other things in a normal day.
I’m a home-health nurse. My days don’t happen at a desk. If building software required sitting down at a workstation for uninterrupted hours, I’d ship nothing. So I built a setup where the workstation is optional — and it turns out the pieces are all things a solo builder can set up in an afternoon or two.
The three pieces
1. A command center for AI coding agents. At home, my PC runs something I built called Mission Control: one dashboard running a fleet of Claude Code sessions — each one an AI developer assigned to a different project. Live terminals, status lights (“working,” “needs your reply,” “finished”), and automatic backups to GitHub every time an agent finishes a task. It’s the difference between using an AI assistant and managing a team of them. Eleven projects move forward this way.
2. A secure doorway to it. That dashboard is reachable from any browser through an encrypted tunnel, with two locks on the door: an emailed one-time code (only my address is on the list), then a PIN. Standing in a parking lot, I can check what my agents finished, answer the one that’s stuck, and start the next task — the same cockpit I’d have at my desk, on a phone screen.
3. A cloud fallback when the PC is off. Claude Code also runs entirely in the cloud — in the browser at claude.ai, or right inside the Claude iPhone app. It connects to my GitHub repositories, does the work on Anthropic’s computers, and hands the result back as a pull request: a neat bundle of proposed changes I can review and approve with a tap. My PC can be a brick and the building continues.
The part that makes it all click
The deploy pipeline has zero manual steps. This website lives in a GitHub repository; anything merged to the main branch is live on nursebuilds.com about a minute later, built and published automatically by Cloudflare. So the phone workflow is genuinely complete: describe the change → AI builds it in the cloud → review the pull request → tap merge → it’s live.
That last tap matters more than it looks. Nursing taught me to never chart “probably done” — you verify, at the bedside. The pull-request step is the software version of that: nothing ships until a human looked at exactly what’s changing and signed off. The AI does the labor; I keep the judgment.
What this actually costs
Less than you’d think: a domain name (~$10/year), free tiers of GitHub and Cloudflare, and a Claude subscription I’d have anyway. No servers to rent, no ops team, no IT department. The tools to run a one-person software shop from a phone are just… available now, mostly free, waiting for someone to wire them together.
Why I’m telling you this
Because the bottleneck isn’t access anymore — it’s knowing this is possible. A year ago I assumed “real” developers had something I didn’t. What they had was a workflow. Now I have one too, and mine fits in scrub pockets.
If you’re a nurse — or anyone whose day doesn’t happen at a desk — with an idea you keep shelving because “I’m never at a computer”: that excuse retired. I’d love to hear what you’d build — hello@nursebuilds.com.
As always: no patient information here, ever. The only thing from work in this post is the parking lot.