About

Who I am

Full stack is less a title here than a working preference. I would rather own a feature from the schema to the last pixel than hand it across a boundary and hope the two halves meet in the middle. Most of what I ship is TypeScript — React and Next.js at the front, Node and GraphQL behind it — with the interface treated as part of the engineering rather than a coat of paint applied at the end.

The result is fewer handoffs and fewer gaps: the person who chose the shape of the response is the same person who has to render it, so the awkward cases get designed away instead of argued about.

How I work

• Start from the data. Most interface problems are a schema that was decided in a hurry.
• Ship the smallest thing that is genuinely finished, then keep it working. Half-built features are debt with a nicer name.
• Read the platform before reaching for a library. A lot of what gets installed is already in the browser.
• Show the work. Every experiment on the craft pages ships its own source, so you can read what actually runs rather than a description of it.

What's on this site

• Work

  Roles I've held, on a timeline, and the projects I've shipped with their stacks and source.

• Craft

  UI experiments, animations and interaction studies — each with a preview, a write-up, and its code.

• Blogs

  Writing on tooling, the web platform, and the parts of shipping software that don't fit in a commit message.

• Contact

  How to reach me, and what to put in the first message.

Elsewhere

• GitHub

  Source for this site and most of the projects listed on it.

• LinkedIn

  Roles and dates, for anyone who needs the formal version.