I build the system behind the product.

I build where product thinking and systems engineering meet. I’m most useful when the problem is still partly undefined: when the workflow needs to be understood, the constraints need to be made explicit, and the software has to survive real use rather than stop at a polished interface.

I tend to follow a project through the whole chain—product shape, data model, interaction design, implementation, deployment, and the operating details that keep it dependable. That has included a bilingual commerce and content platform, a private multi-currency household ledger, and small developer packages that bridge tools which were not designed to speak to one another.

I care about clarity for both sides of the system. The person using it should understand what happened and what to do next; the person maintaining it should be able to see the invariants, failure paths, and recovery options. Good software is not only capable. It is legible, honest about its limits, and safe to change.