Everything starts as a problem and a sketch. I decide what the thing is, who it's for, and how it should feel before any code exists. Ten years of product design doesn't turn off — it's why a five-party solar workflow can feel like one product instead of five portals.

Then the structure — where state lives, what talks to what, what breaks when money or trust is on the line. This part doesn't get delegated. Not to people, not to models. It's the difference between billing that can't double-fire and billing that usually doesn't.

I run coding agents the way a lead runs a team: tight specs in, diffs out, everything reviewed. It's the biggest change to my craft since I learned to design — and it's how seven products shipped this year with a team of one.

Nothing ships on vibes. Eval harnesses, golden tasks, thresholds that kill a system automatically if it degrades — and a human required to re-arm it. The question isn't whether it demos well. It's what happens the ten-thousandth time it runs.