Skip to content

04 / About

The person behind the pixels

Still curious. Still building.

I’ve been building software for about 15 years. I still like it.

The tools change.
The interesting part stays.

I build products, lead frontend teams, and spend a lot of time thinking about architecture. Not architecture as a diagram that nobody looks at again. Architecture as the decisions that make tomorrow’s work easier or harder.

The longer I do this, the less interested I am in cleverness for its own sake. I want to understand a system. I want the next person to understand it too. And I want us to be able to change our minds without rebuilding everything.

That carries into how I think about leadership. Give people context. Be clear about what matters. Help when something gets in the way. Then leave enough room for people to surprise you.

Good architecture buys freedom.
Good leadership should do the same.

AI has given me a new set of questions to obsess over. What should we automate? What still needs judgment? What changes when building software becomes a much faster part of solving the problem?

I don’t have all the answers. Working through those questions, preferably by building something, is a pretty good way to spend my time.

A few familiar tools

Tools, not an identity.

I’m comfortable changing the stack when the problem calls for it. This site happens to bring a few favorites together.

  • Vue
  • TypeScript
  • Nuxt
  • Python
  • Three.js
Have something interesting in mind?Tell me about it.