How I work

I don't write code.
I build production systems.

No CS degree. No bootcamp. Twenty-five years in operations, then one day I described a problem to an AI and it wrote a working solution. That was the shift. Now I build production systems by having conversations — explaining what I need, testing what comes back, iterating until it works. People call it vibe coding. I call it the first time building software has made sense to me.

The process

Problem in, system out

01

I hit a wall

Every system I've built started the same way — a manual process that was too slow, too expensive, or too dependent on people being awake. Not a product idea. A frustration.

02

I describe what I need

I open Claude and explain the problem in plain English. Not pseudocode. Not architecture diagrams. Just: here's what's broken, here's what the fix looks like, here's how I'll know it works. The same way I'd brief a new hire.

03

I build in conversation

I don't plan the full system upfront. I start with the smallest piece that proves the idea works, test it, then ask for the next piece. Each round takes minutes. By the end of a session I have something running.

04

I break things and fix them

Nothing works the first time. I read error messages, paste them back, describe what I expected versus what happened. Debugging is just another conversation. The AI writes code. I decide if the output is right.

05

I ship it

When it does what I need, it goes live. No staging environment drama, no sprint planning, no waiting for a team. One person, one tool, problem solved. Then I move on to the next wall.

The honest part

I don't pretend to be an engineer. I know what each system does, I know when it's wrong, and I know how to fix it. That's the same skill set I've used for 25 years managing complex operations — you don't need to do every job to lead effectively.

Why it works

The advantage isn't technical skill. It's knowing which problems are worth solving. Twenty-five years of running operations means I don't build interesting demos — I build the thing that eliminates the 4am phone call, the manual report nobody wants to compile, the process that breaks every time someone goes on vacation.

The AI writes the code. I bring the judgment about what to build and why it matters. That combination — operator intuition plus AI capability — is how one person builds seven production systems without an engineering team.

See what this process produces.

VIEW THE WORK