About
Technical judgment is the product.
I learned by building and operating real systems — not through a conventional software-engineering path. The work taught me that the most useful technology is usually the kind people do not have to think about.
Simple is an operating advantage.
I prefer systems with clear state, understandable interfaces, and boring failure modes. A workflow should not need a training manual to explain what it is doing or who is responsible for it.
I’m comfortable challenging whether AI is needed at all. I use AI when reasoning is useful. I use normal software when it isn’t.
AI-assisted development, openly.
I use coding agents such as Claude Code and Codex aggressively as implementation leverage. I remain responsible for architecture, requirements, review, testing, deployment, and operational outcomes.
What matters is whether the system works, can be understood, and keeps working — not who manually typed every line.
The correct action should be the easiest action.
What I bring to a messy company
I can map the actual process, identify what should be a decision versus a workflow, and build the technical layer beneath it. I communicate that work in plain English with the people who have to run it.
What I optimize for
Reliable ownership. Clear state. Recoverable failures. Appropriate human approval. Systems that improve operations without creating a new pile of software to maintain.