I came to code the long way round.

Long before any of it was a job, I was thirteen, making my friends' Bebo and MySpace profiles for fun. It never occurred to me that building things on computers was a job you could have. You can't be what you can't see, so I came at it sideways.

I build for the web now. React, Next.js and TypeScript, for agencies, a software consultancy, and editorial publishers like the Financial Times. I got here through sound and film, and the three have more in common than the job titles do. Each one is composition: arranging things so they land for the person on the other side. A mix, a cut and an interface are the same instinct in different mediums.

Music came first. I loved writing and producing it, so I studied sound design at university. Sound is all arrangement: where something sits, what it does to you, what's missing.

I lived with filmmakers there, and shoots were the most fun I'd had, so I picked up a camera. A wedding, a short film shot in one foggy morning in Bath, twelve films in twelve months just to get better. Same instinct with more to hold: deciding what someone sees, and when, and how long you make them wait for it.

The computer thread ran underneath all of it. I'd used Windows until I was seventeen, then got a job at Apple, switched to a Mac, and learned my way around it on the shop floor and at home until I knew it cold. I delivered Apple's "Learning to Code with Sphero" course there, getting beginners to write the few lines that sent a little robot across the floor. Watching it click for a room of people was the pull. I wanted to be the one building, so I moved into the web.

That's where it's landed, code at the centre now. A booking flow that lifted spend per booking by 48% in its first week. And Chork, a climbing app I design and build, that my friends and I use.

For years the rest of it sat in different places, or nowhere. The films on a YouTube channel, the code on GitHub, the audio more or less lost. You move on to the next thing and set the last one down, and after a while the through-line stops being visible, even to you.

This site is me putting it back in one place. Code, audio, video, and a blog, on equal footing, each with its own colour. It's a custom build: one persistent shell that morphs in place as you navigate, so the colour changes without a page reload, cross-fading instead of sliding through the muddy browns in between. The blog can put a real, working component straight into an article, not a screenshot of one. My first post measures the token cost of four CSS approaches and drops the site's actual button into the page for you to click.

It's not three half-careers. It's one instinct in three mediums, composing something for the person at the other end, and the web is where it all comes together. I'm open to permanent roles and freelance or contract work, frontend-first, full-stack when it's needed. If you've got something that needs building, the links are all on the site. Make yourself at home!