Coordinated Omission: The Reason Your Latency Numbers Are a Lie
Coordinated omission is a measurement problem that shows up in a lot of load testing setups, and it has a habit of making latency numbers look much better th...
Hello there, stranger. I’m glad you’re here 👋.
I’m a software engineer working at Morgan Stanley, building systems in the finance space. Most of my day-to-day work is backend focused, thinking about how services communicate, how data flows through systems, and how to make things reliable when they are under real pressure. I also enjoy working across the stack when it helps bring an idea fully to life.
Over time, I have realized that what I really enjoy is not just writing code, but understanding why systems behave the way they do. I like thinking about trade-offs, about how small decisions affect long-term complexity, and about how to keep things simple without cutting corners. There is something satisfying about building software that feels calm and predictable even when the environment around it is not.
This website is a reflection of that curiosity. It is where I document ideas I am exploring, projects I build for fun, and things I am trying to understand more deeply. Not everything here is meant to be practical or polished.
If any of that resonates with you, welcome. 🙂
Coordinated omission is a measurement problem that shows up in a lot of load testing setups, and it has a habit of making latency numbers look much better th...
It started with a file that was slightly larger than it should have been. There were no crashes and no alerts, just an export that didn’t look quite right. W...
If you’ve ever worked with Kafka in production, you’ve probably dealt with consumer group rebalancing at some point. Most of the time, it’s just background n...