About
I’m a software engineer. For most of my career that meant building systems. These days I find myself between security, compliance, infrastructure, site reliability, and release engineering, along with technical writing and quality assurance, helping those disciplines collaborate.
I’m not an expert in any of those fields. The people I work with are. What I have is enough exposure to each to notice when two teams are solving the same problem in different words, and enough software engineering to connect the dots.
What you’ll find here
Writing that starts with a question. Not the rhetorical kind, the kind that comes out of a thought experiment. Something breaks, or works when it shouldn’t, and I want to know why. Then: maybe that’s the reason. If it is, what happens when we push on it? Usually something instructive falls out. Sometimes it doesn’t, and I say so.
The lab is hardware, notes, sources, and experiments. It is not one project. Some pages are polished, some are inventory, and some still say what I have not checked yet.