Notes from a systems engineer.
I build software and infrastructure for systems that need to stay understandable, testable, and maintainable after they leave development.
This site is where I keep technical notes, implementation details, design tradeoffs, and writeups from the parts of engineering that usually become interesting only after real systems start interacting.
What to expect
I want this section of the site to collect the things I usually wish someone had written down before I had to piece them together from documentation, source code, man pages, packet captures, logs, and trial and error.
Some of it will be narrow: a strange integration issue, a test boundary that made a system easier to reason about, a networking detail that changed the shape of a design, or a small implementation choice that mattered more than expected.
I am not trying to turn every note into a polished tutorial. The useful part is usually the constraint, the mistake, the assumption that failed, or the detail that finally made the system make sense.