About

I’ve spent most of my career building and running systems that look stable on dashboards but behave very differently in real life.

That gap — between what we think a system is doing and what it’s actually doing — is what pulled me deeper into infrastructure, DevOps, and eventually ML and data systems.

This site is where I write down what I’m learning while trying to close that gap.

Why I Write Here

A lot of my real learning didn’t come from courses or polished blogs.
It came from production incidents, half-broken migrations, unclear alerts, and long debugging sessions where the root cause wasn’t obvious — or wasn’t even technical.

Most write-ups skip that part.

Here, I don’t.

I use this space to think through problems that don’t have clean answers yet — things like:

• Why data pipelines fail quietly
• Why “observability” often becomes noise
• Why ML systems break in ways traditional infra never did
• Why automation still needs human judgment

Sometimes the writing is structured. Sometimes it’s just notes that grew into an idea.Fresh content, delivered

Stay up to date with new content sent straight to your inbox! No more worrying about whether you missed something because of a pesky algorithm or news feed.

What You’ll Find

I mostly write about:

• DevOps and infrastructure at scale
• MLOps and data reliability
• Observability beyond metrics and alerts
• Using AI where it actually helps engineers, not where it just sounds good

I’m less interested in tools and more interested in behavior — how systems change under load, during failure, and over time.

If something worked only in a demo or a diagram, I’m usually skeptical.

How I Approach Problems

I don’t believe in perfect architectures.

Every system is a set of trade-offs, made under time pressure, with incomplete information. The interesting part is understanding which trade-offs matter and when they stop being valid.

So I tend to:

• Question defaults
• Look for first-order causes before adding complexity
• Prefer simple systems that fail clearly over clever ones that fail silently

When I’m wrong, I try to document that too.

What This Site Is Not

This isn’t a highlight reel or a résumé.

It’s closer to a working notebook — a place to explore ideas before they’re fully formed. Some of them may turn into real projects. Some won’t. That’s fine.

The goal is clarity, not polish.

If This Resonates

If you’ve ever stared at a dashboard that said “all green” while production was clearly on fire, you’ll probably feel at home here.

Read, disagree, borrow ideas, or ignore them entirely.
This site exists mainly so I can think better — anything else is a bonus.