How I Ship Without Knowing How to Code

I build software for my lab, and I still can't read most of the code. This post is the loop that makes that possible, because the loop — not any one feature — is the story. Everything I ship, ships through this.

It starts with plain English. I describe what I need the way I'd brief a person standing in the lab: here's what the morning looks like, here's the question everyone keeps asking, here's what I want on one screen so they stop asking me. No technical words, because I don't have them.

The AI writes the code. I don't read it. I look at what shows up on the screen and judge it the way I judge everything else in my business: does this match reality? First versions usually hand me too much — a wall of everything, the kind of screen that impresses in a demo and gets ignored by Wednesday. So I push back, in English: the technicians need three answers in five seconds, cut the rest. It cuts the rest.

A few rounds of that, and the thing ships. It's the same loop I use with people, minus the feelings.

Now the failure mode, because this doesn't work as an honest post without it. The AI is confidently wrong in ways a confident person would be fired for. It will show numbers that look plausible — tidy, formatted, believable — and are wrong. It will fix the thing you asked about and quietly break the thing that worked yesterday. Some weeks the thing I shipped on Monday is broken by Wednesday. I'm not confessing to a rare event. I'm describing a line item. You don't skip that tax; you budget for it.

Notice what my defense is, though. It isn't reading the code — I can't. It's knowing my business cold. I look at the same numbers every morning before 7am, so when a screen disagrees with reality, I know which one to believe. Wrong-but-plausible data might slip past a programmer who doesn't know the lab. It doesn't slip past the guy who knows what the board should say before the page loads. That's the standing trade: the AI brings the code, I bring the reality check.

Why ship anything built this way? Because the customer is me. This software runs my lab, in front of people who know the work cold, so wrong gets caught fast and fixed the same day. I'm not selling it to strangers. I'm using it to run the thing I know best — which is exactly why I get to be this aggressive about shipping.

Ten years ago, any one of these tools would have been a quote from a software company and a long wait, and I wouldn't have built it at all. Now it costs me plain English, a few rounds of pushback, and a budgeted amount of wrong. I'll take that trade every time. The posts in this section are the log of the loop running — including whatever breaks.