Distributed systems and systems engineering.

This is where my curiosity has been pulling me. The things I've built kept bringing me back to the same questions: what happens when two things try to do the same job at once, when a message arrives twice, when a server disappears halfway through a task, or when one machine stops being enough. I've answered some of those in practice. I want to understand them properly, from the ground up.

I'm still finding my way in. Right now that means reading the papers and books behind the tools I already use, things like consensus, replication, queues, consistency and failure, and rebuilding small versions of them myself to see where they break.

I think this is the part of engineering that will shape my career the most. The systems I want to build should keep working when traffic grows, machines fail and the network misbehaves. Getting there means knowing why things work, not just how to use them. This page is where that work will live as it takes shape.