About

I am a designer and engineer with more than ten years of experience building software across large enterprise systems, early-stage startups and my own products.

Today I work at the intersection of technology, people and business — usually with small teams who need one person who can hold all three at once.

My first years were spent inside a system where mistakes had real consequences. That taught me reliability, testing, and the discipline of changing something carefully.

Later, smaller teams pushed me past implementation. I became interested in architecture, interface design, domain knowledge, and how a group of people arrives at a good technical decision together.

That changed how I look at engineering:

The code matters. So does everything around the code.

Building my own products pushed that further. I learned what it means to start from a problem, design something, ship it, and then face the harder question:

Will anyone actually use it?

Distribution, trust, pricing and positioning can matter as much as the product. That is uncomfortable for an engineer, and it is worth learning anyway.

The tools are changing quickly. I use them heavily, and I am more interested in what they change than in how much faster they make me.

• What happens when software can be produced faster than anyone can read it?
• How do we keep understanding, quality and responsibility intact?
• If building gets cheaper, does judgement become the scarce thing?

Those questions sit behind most of what I write about and experiment with.

I spend my time away from the screen gardening, baking and running.

A surprising number of my ideas start there. I like activities where you observe, adjust a little, and slowly understand how the whole thing behaves.