Hello World

I’ve been a data engineer for over a decade. I’ve built pipelines that process hundreds of thousands of events per minute, managed petabyte-scale warehouses, and shipped systems that broke in ways I didn’t think were possible.

I never wrote any of it down.

That’s the thing about infrastructure work — you solve hard problems, learn expensive lessons, and then move on to the next sprint. The knowledge stays in your head or buried in design docs that nobody reads after launch.

I want to change that, at least for myself.

This blog is where I’ll write about the problems I actually face at work. Not tutorials. Not “how to set up Kafka in 5 minutes.” The real stuff — why we chose one architecture over another, what broke in production and why, how we cut costs by 90% on a system everyone assumed was already optimized.

I’ll write about data engineering, streaming systems, ML infrastructure, and cloud architecture. I’ll include code when it helps and skip it when it doesn’t.

One rule: every post has to say something I wish someone had told me earlier.

If that sounds useful, stick around.