When something goes wrong in a distributed system, the hardest part isn’t fixing it — it’s understanding what happened. This post walks through a technique for tracing a single request across multiple services.
This blog is about building software — the messy, iterative, satisfying kind. Expect posts on distributed systems, tooling, debugging war stories, and the occasional deep dive into something obscure.
The name is a philosophy: things rarely work the first time, and that’s fine.