About

I’ve spent most of my career designing, securing, and operating complex infrastructure: Linux systems, enterprise networks, cloud platforms, and distributed applications. Working across those layers has given me a clear standard. A system must have a reason for its shape. Its parts must serve its purpose. Its design must hold up when someone depends on it.

First principles

I want to understand a thing well enough to make my own decisions about it. That means following a protocol down to its assumptions, an operating system to its mechanisms, or a radio to the signal. The same discipline applies to security: know what you trust, establish the boundaries, and test what happens when those assumptions fail.

I build from that understanding. Familiarity alone is no justification for a design. Every dependency brings obligations; every abstraction leaves something out. I choose them deliberately and take responsibility for the result.

The work

This site records the work and the reasoning behind it. Tutorials, project logs, architecture notes, and essays grow out of systems I’ve built, questions I’ve investigated, and decisions I’ve had to defend. I write about technology and the policies that determine who controls it.

The standard is the same on the page as it is in the system: make the reasoning clear enough to examine, and let the result bear scrutiny.

Off the clock

Away from the keyboard, I read history and philosophy, experiment with hardware, and spend time outdoors. History gives decisions their consequences. Philosophy makes their premises explicit. There is also value in a day outside, with no system demanding attention.