01About
Seven-plus years of turning product ideas into things people actually use.
I'm a full-stack engineer and product developer. The part I care about most is the whole — not just shipping a feature, but understanding why it exists, what it should feel like, and what it costs to run once it's live.
Day to day that means React and Next.js on the front, Node and Mongo behind it, and AWS or Azure holding it up. It also means the less glamorous work that decides whether a product succeeds: frontend performance budgets, Core Web Vitals, and SEO-driven engineering that gets the thing found in the first place.
Away from the editor I'm a fairly ordinary tech guy — gaming, music, and a long-standing weakness for good hardware.
02How I work
End-to-end product vision
I work from the problem, not the ticket. Scoping, architecture, build, and the follow-through after launch — I'd rather own the whole arc than hand it off halfway.
Performance as a feature
Frontend performance optimisation is a specialisation, not an afterthought. Bundle budgets, render paths, Core Web Vitals — the things users feel before they can name them.
SEO-driven engineering
Marketing-adjacent development: rendering strategy, structured data, and the technical decisions that determine whether anyone ever finds what you built.