Make the system understandable
I pay attention to the states, rules, and recovery paths behind the screen.
About
I trained as an architect. Now I build software.
I trained as an architect, then moved into software. I still work the same way: understand the parts, find the constraints, and make the result useful.
I still learn best by making things.
From architecture to software
I brought the same habits into software.
Architecture taught me to think about the person using a space, the visible structure, and everything holding it up. I approach software the same way.
These days I move between product decisions, interface design, code, integrations, and the unglamorous operational work that keeps a product usable.
This site is a working record of my projects, the things I have learned, and the questions I am still trying to answer.
How I work
Finish a small version first
I would rather complete one working path than leave a dozen impressive fragments.
Learn on real projects
New technology starts making sense once I have to ship and maintain it.
Own what ships
I stay with the maintenance and operational problems that appear after launch.
Contact
Want to talk? Send me a message.
For product work, collaboration, or a useful conversation.