I build software the way I’d want to use it.

I don’t think of design and engineering as two separate jobs. I draw a screen in Figma and then write the component for it, and the result is better for never being thrown over a wall between two people. Left to my own devices, I’ll build the thing that builds things: a design system instead of one more screen, a runtime for widgets instead of one more widget. Slower on the first feature, much faster by the tenth.

After that it’s the small stuff that adds up. A loading state should do more than reuse the empty one’s layout. Color lives in tokens, so a redesign is one edit instead of a hundred. And I’ll drop an animation before I ship one that’s only there to look busy.

Day to day, that’s product work with a team. In whatever time is left, I build my own tools, the ones in the work section: a live analytics dashboard, a component library for data-heavy interfaces, and a few more still in progress. Some of it solves a real problem I ran into. Mostly, though, I just learn a tool far better by building one than by using someone else’s.

Away from the keyboard I’m usually training, traveling, or making music. There’s a DAW plugin I keep meaning to build, which is the same story as the rest of this page: I can’t use a tool for long before I start wanting my own version of it.