I started at the register level.

The first code I shipped controlled a water pump inside a diesel truck engine. Since then I have laid out circuit boards and pushed Go services past 60,000 transactions a second. These days I design systems and then build them, in Rust when the choice is mine. The layer keeps changing. The question doesn’t: what is the machine actually doing?

11/2024 – present
Platform architecture: auth, audit, security posture. OpsMx

Now

I am a principal engineer at OpsMx, working on how software gets delivered and secured. Lately that has meant the architecture underneath it: authentication and authorisation, an audit service, and a context service that hands cloud security posture to AI agents over MCP. Right now it is performance: why the graph database restarts, how it should be sized, and what it takes to get a query back in under a couple of seconds.

My first six years were embedded systems and automotive software, which is where caring about footprint becomes a habit rather than a preference. Since then I have worked across most of the stack: solution design, backend, DevOps, testing, and enough UI to be useful in the conversation. I would rather inspire a team to build something together than monitor them building it.

Most of my own time goes to Rust, and most of that goes to the two things below. If you are building something interesting, I would like to hear about it.

Building

Selected work

The full history

Writing

Occasional notes on Rust, Go and whatever I am taking apart. Read the blog, or take the feed.