Back to Use Cases
Development

Voice-First Development: How I Ship Code Without Touching a Keyboard

This entire website was built by talking to my AI colleague. Not voice memos. Real-time conversation.

I'm walking through Lisbon right now. Talking to my digital colleague. In 2-3 minutes, I'll have a preview URL to check the changes live. Not "by the time I'm home." Right now. While still walking.

How It Actually Works

I talk to my AI colleague via Telegram. Not voice memos—a real conversation. It runs on my Mac at home, reads my vault, understands the context, and executes immediately. "Simplify the menu to 4 items and add a Use Cases section." That's my instruction. My colleague: - Finds the right files - Writes the code - Commits to QA branch - Pushes to GitHub - Vercel builds automatically 2-3 minutes later: preview URL in my hand. I check it on my phone, give feedback, colleague adjusts. Another 2 minutes. Done. No laptop. No IDE. No typing. Just conversation.

The System Behind It

This works because of three things:

  • Context persistence — My AI knows the project structure, the coding patterns, the file locations. I don't re-explain anything.
  • QA branch workflow — Nothing goes to production without my explicit approval. I review on my phone, merge when ready.
  • Governance files — My AI knows what it's allowed to do. It can write code and commit to QA. It cannot deploy to production without my GO.

The Reality

This page you're reading? Built this way. While I was walking. The menu went from 10 items to 4? Conversation while making coffee. Checked the preview on my phone. Done. The Portuguese translations? Talked through them during a walk. Reviewed. Approved. Live. I ship more features from my phone than most developers ship from their desk. Not because I'm faster—because the friction is gone. No context-switching. No "I'll do it when I'm at my laptop." I talk. My colleague executes. I verify. That's the loop.

Why This Matters

This isn't about being lazy. It's about removing the gap between thought and action. When an idea hits you during a walk, in the shower, at dinner—you shouldn't need to "remember to do it later." You should be able to act on it immediately. That's what this system enables. Voice in, deployed code out. From anywhere.

Want to build something like this?

I help people design AI infrastructure that actually works. Not chatbots. Not wrappers. Real systems.

Let's talk