I Ship Sites By Talking, Not Typing

This morning I walked my dog. By the time I got home, my Rust app had three new features. I did not open a laptop. I did not sit at a desk. I talked into my phone.

That is what this post is about.

The Kit

I use three small tools. Stacked together, they change everything.

Voice
SuperWhisper
Claude Code
Pull Request
  1. SuperWhisper turns my voice into clean text. It is faster than I can type.
  2. Claude Code reads that text. It writes code. It opens branches. It opens pull requests.
  3. MCP servers are tiny bridges. They let Claude reach into apps like Linear and Gmail. Say "make a ticket," and a real ticket gets made.

That is the whole kit. Nothing else.

Example 1: This Website

Look at the bottom-right corner. That is my face. Click it. A small text card pops up.

You probably did not notice that the styles on this page never go stale on your phone anymore. You probably also did not see the live Discord widget over on the Auteurs post.

I shipped all three of those things this week. By talking.

Each one is a real change to a Rust codebase. I typed none of them.

Example 2: A Game For My Son

His name is Dean. He is learning math. So I built him a game.

The stack is built for a kid using an iPad. Local-first means the game works without internet. It only talks to the cloud when it needs an update.

GitHub
The iPad only reaches out when there is a new update. The rest of the time the game is on its own.

Why does that matter? Because Dean uses his iPad in the back of the car. Wifi is flaky. The game has to work anyway.

The fun trick: the code heals itself. If something breaks, the next prompt fixes it. I am not afraid of breaking things, because nothing stays broken for long.

I also use Codex to make the artwork. I asked it for bestiaries — the monster lineups from classic Final Fantasy games. It came back with creatures Dean had never seen anywhere else. He loves them.

There is no perfect tech stack. This one fits its job: a learning game my son plays on an iPad, hosted free on GitHub, that I can ship to him every weekend.

Example 3: Broadcast Software, From My Phone

There is a second project called Screen. It is broadcast software — the kind a streamer would use to go live. Real, sellable software, built on serious tech:

I have no business writing software like this. I am not the right kind of engineer. But I am doing it anyway.

Here is how. I am out walking the dog. I think of something. I open my phone. I talk into it. I paste the words into Claude Code. It makes Linear tickets. I write one more prompt: work through these. It chews through them while I keep walking. If it gets stuck, my phone dings. I answer. It keeps going.

Z z z
I wake up to merged pull requests.

This is the part that still feels new — work happens while I sleep. Long-running tasks. I wake up to four merged pull requests. I review them with my coffee. The cycle keeps moving.

Why This Matters For You

I co-manage Uber.com and Uber Eats. These are billion-dollar websites. They are hard to build and hard to keep running. The teams behind them are large and expensive. There are good reasons for that.

But here is a question. What if a small coffee shop in your town could have the same quality website? What if a local florist could have the same checkout flow? What if a hair salon could have the same kind of AI helping it?

Small and medium businesses are about to become their own Shopify. Their own brand studio. Their own engineering team.

The way they will do it is by hiring people like me — and there are about to be a lot more of us — who can ship at full scale because the tools no longer slow us down.

I think of it like real estate. Real estate agents serve neighborhoods. I want to serve small businesses, neighborhood by neighborhood, brand by brand. Build them a site. Build them a checkout. Run it for them, full service. A tiny team of humans, with an enormous team of AI behind us.

The Floor Is Rising

Here is the line I keep coming back to.

We are only bound by our ideas now.

Not by typing speed. Not by which framework we know. Not by the size of our team.

If you can describe what you want — clearly, in plain words — you can ship it.

This post is the proof. So is the Discord widget on the next article over. So is the math game my son plays.

I will show you more soon.