About This Blog

What this is

This is my personal blog — a place where I write about things I’m learning, building, or find genuinely interesting.

It’s not a tutorial site.
It’s not a portfolio.
It’s a place to think clearly, in public.

What I write about

The core is technical depth — backend systems, infrastructure, system design, and the kind of understanding that holds up when things break.

But I also write about:

• Side projects I’m working on
• Interesting things I’m reading or watching in tech
• Concepts I’m trying to make stick by explaining them out loud

If something catches my attention and I think writing about it will make me understand it better, it ends up here.

Why write this down?

I don’t trust shallow understanding.

If I can’t explain how something works without hand-waving, I assume I don’t understand it yet. Writing is how I test that. Every post starts with something I think I understand and ends only once the underlying behavior is clear.

The secondary reason: this is public, which means it’s useful to anyone else trying to build the same understanding.

The kind of learning I care about

I’m interested in how systems actually work — not just how to use them.

That usually means:

• Starting from first principles
• Looking at what’s actually happening on the wire
• Paying attention to boundaries, assumptions, and failure modes
• Removing abstraction until the core idea is visible

If a concept can’t be explained simply, I assume I don’t understand it yet. This blog exists to fix that.

Who this is for

Primarily, this is for me.

But if you’re someone who cares about building real understanding over collecting tutorials, you’ll probably find something here worth reading.

I’m learning as I go. This is just me making the process visible.