I build reliable systems and tools, usually close to the metal.
Most of my work lives at the boundary between software and infrastructure: Linux, networking, distributed systems, and the failure modes that appear when those layers interact. I’m especially interested in eliminating the kinds of subtle, cross-layer issues that make systems unpredictable — timing problems, resource contention, and failures that only emerge under real production load.
I tend to work Rust-first for new systems because it lets me build software that is both high-performance and predictable over time. I care a lot about correctness, clarity, and long-term maintainability, especially in environments where software runs continuously and small mistakes accumulate.
A lot of my career has been spent making brittle systems boring again: reducing outages, removing pathological behavior, and turning production mysteries into things that can be reasoned about. I enjoy debugging across layers — from application code down into kernels, schedulers, and network devices — and I’m happiest when a system becomes simple to understand and trust.
Outside of work, I spend a lot of time experimenting with personal projects, infrastructure at home, and automation — treating them as small systems to explore how reliability and ergonomics actually feel in practice. I’m also interested in market structure, Bitcoin, and the mechanics of financial systems, especially where latency, incentives, and engineering intersect.