The first thing I built was back in 2011. I was only 9 so I used a drag and drop tool to create an app for my Dad's Android phone that would simulate a golf club. A quick swing of the device would trigger a simple function to randomly play a sound and give you a score.
I'm a bit older now, and a novelty app isn't much to shout about, but the 15 years since then have given me plenty of chances to make mistakes and learn how to build things properly. Technology has changed a lot, but my curiosity remains the same as it was all those years ago. I still have the most fun when I'm working with something unfamiliar, which is why I've pushed to stay as multidisciplinary as I can. My interests are wide-ranging, from designing software to building hardware, at companies of very different sizes.
I'm motivated by end users. The people who actually have to use the thing and live with the decisions we make. That's why I care so deeply about the impact of my work. It's not just about the screens they see or the buttons they press, it's also the craftsmanship that goes into making the stuff underneath the bonnet.
I put a lot of emphasis on quality. I love designing efficient, scalable architectures that can be changed later without tearing everything up. Sure, rarely does anyone know exactly what they'll need six months from now, but building things properly doesn't have to slow you down. It can be the thing that speeds you up.
Nowadays, anyone can use AI to write code. It has opened up incredible opportunities, but programming has always been merely one part of the process. The most useful skill I've acquired is breaking down a complicated problem into pieces and explaining them to whoever's in the room at the right level.
Working in innovation has also taught me that quite often the stakeholder doesn't know what problem they need solved. When a process has worked well enough for years it's hard to see past it from the inside. That's where someone from outside earns their keep, by asking the obvious questions nobody has been asking.
So often the first question shouldn't be "how should we build this?" but "what should we build?". On this website, you'll find my past answers to both. I hope you enjoy looking around.
Here are some of the things I've built over the years. From working with big companies to volunteer groups, no problem is too large and no solution is too small!

A three-person team built, tracked and launched a weather balloon with cameras and a radio tracker to nearly 39 km, then recovered it 5.8 km from the launch site.

An open-source Terraform module that deploys Next.js to AWS on a fully serverless architecture.

An ETL pipeline using CLIP, LLMs and Computer Use that converts a legacy VB6 boiler diagnostics application into a cloud-native, RAG-ready format, now being turned into a SaaS offering with several SME customers.

Centrica's internal AI ideation platform, which I designed, launched and own. It is the company-wide source of truth for innovation projects, with thousands of active users and external procurement interest.