I’m a technical systems builder and hands-on learner who moves between software, infrastructure, networking, hardware, security, automation, APIs and experimental AI.
Documentation gives me the terrain. Experimentation is how I actually understand the landscape.
I’m most interested in what sits underneath the polished surface: architecture, dependencies, failure modes, hidden assumptions, recovery behavior, and the weird edge cases that reveal how a system was really designed.
I tend to work by assembling something real enough to test, observing where it breaks, then reconstructing the mechanism from the evidence. That often means moving across layers instead of staying inside one specialty.
The goal is not to collect technologies. The goal is to understand the system well enough that the tools become interchangeable.
These are patterns, not rules carved in stone.
When something fails, isolate where the failure crosses from one layer into another instead of guessing at symptoms.
A live API call, deployed service, measured result or reproduced bug teaches more than a diagram that was never exercised.
Unexpected behavior is often the most valuable documentation a system can give you.
A repository can be obsolete while the underlying idea is still worth pursuing through a better tool or architecture.
I also care about the history of technical work—especially my own. Old projects are easy to misremember as either more complete or more pointless than they really were. This site is partly an attempt to keep that record honest.
Outside the technical side, I’m interested in games, music, visual art, unusual technology, philosophy, fishing, and the occasional idea that starts as “I wonder if this is possible” and becomes several weeks of infrastructure.