About

I'm a backend developer. Most of my work lives below the UI: HTTP and gRPC services, database schemas, background workers, and the unglamorous plumbing that decides whether a system holds up at 3am.

I work primarily in Go and Node.js. Go for services where predictable latency and straightforward concurrency matter; Node where the ecosystem and iteration speed win. Underneath both, usually Postgres — I'd rather push work into the database and understand the query plan than add a cache and hope.

The throughline in what I enjoy is legibility: systems whose behaviour you can reason about from the code, schemas that encode the real constraints, and logs that tell you what happened rather than that something happened. Most production incidents I've seen came from a system being harder to understand than it needed to be.

Outside of work I read more systems papers than is strictly reasonable, and occasionally write up what I learn.