Distributed Systems
Failure boundaries, coordination, latency, and the design of services that remain understandable under stress.
Independent systems research
Making complex systems easier to see.
We study the edges between software, networks, and people—then turn what we learn into clear notes and small, practical tools.
Areas of inquiry
Useful questions, carefully framed.
Our work stays deliberately small: understand one behavior, describe it plainly, and leave behind something another person can inspect and adapt.
Open Protocols
Small, legible interfaces that make independent implementations and long-lived tools possible.
Operational Clarity
Observability and documentation that help people reason about what a system is actually doing.
Recent notes
From the field notebook.
Compact observations from experiments, incident reviews, and ongoing reading.
A Smaller Failure Domain
Why the most useful boundary is often the one a person can hold in their head.
Read the summary →Latency Has a Shape
Looking beyond averages to see the pauses and clusters hidden inside a request path.
Read the summary →Notes on Durable Interfaces
What makes a small protocol remain useful when its original context disappears.
Read the summary →Selected projects
Small tools for closer inspection.
Research concepts that make network behavior visible without pretending the picture is the system itself.