I build the systems that other systems depend on.

I started in silicon. At AMD–Xilinx I wrote the Python and DevOps automation that sat under chip design — license servers, LSF clusters, scheduler tooling, the unglamorous infrastructure thousands of engineers depended on every day. It wasn’t headline work, but it taught me how production systems actually behave when they’re under real load.

From there I moved into product development. Today I’m at IBM working on confidential computing — LinuxONE and Hyper Protect Virtual Servers. On the open source side, I lead the contract-tooling effort: contract-go (the Go SDK), contract-cli (the developer-facing tool), and the Terraform provider. Together they handle the cryptography so customers shipping confidential workloads don’t have to.

Outside IBM I take on a small amount of freelance and consulting work — websites, internal tools, and Linux automation for individuals and small teams. I own the full build: requirements, architecture, code, deploy. If you’re hiring or have something interesting to put together, say hi.

Off the keyboard, it’s wheels — bikes, cars, the bicycle when the route deserves it. Same impulse, really: how does this thing work, and can I make it work a little better? Some of my best thinking happens with grease on my hands.

There’s an indoor version of all this too: a soldering iron, a ham radio, and the kind of circuits that take longer to debug than they should. Same engineer, smaller workbench.

And when there’s a road I haven’t ridden, I tend to find a way to ride it. Travel keeps me curious — new cities, new food, new ways people solve familiar problems. The best ideas I bring back are usually the ones I wasn’t looking for.