I design things, make things, and build the software that runs inside them. Twenty-five years of engineering experience sits behind that, across a wider range than most careers cover — and the thread running through all of it is the same: complex problems, long lifespans, and real consequences when they're got wrong.

The software half of that has taken me through desktop and enterprise applications, web platforms, embedded systems on constrained hardware, and scientific computing. Code that informs a clinical decision is held to a different standard than code that serves a page, and working to that standard has shaped how I approach everything else.

The other half is physical. Design, fabrication and prototyping — the work of getting from an intent to an object that exists and functions. These two sides are usually treated as separate trades, which is exactly why projects stall at the boundary between them: the mechanical side waits for the software side, and nobody owns the middle. I'm comfortable owning the middle.

Where I work

Design Concept through technical drawing, with how it gets made kept in view throughout.
Fabrication One-off and small-batch parts, materials, assembly and finishing.
Prototyping Fast, honest iterations that answer the risky question before the money goes in.
Technical leadership Architecture review, build-versus-buy, due diligence, and mentoring.
Embedded & hardware Low-level work on constrained hardware — where the physical and digital meet.
Software Scientific computing, desktop, web, integration, and long-lived codebases.

Open source

I contribute to the Open Systems Pharmacology suite — an open toolchain used by researchers and industry for modelling how drugs behave in the body. It's a good example of the kind of project I like: technically demanding, openly developed, and genuinely used.

More of it is on GitHub.

Let's talk

If any of this lines up with what you're working on, I'd like to hear about it.