hello world

i've been meaning to start writing for a while now. not because the internet needs another tech blog — it really doesn't — but because writing forces me to actually understand what i'm building.

there's a gap between "i got it working" and "i can explain why it works." shipping code is one thing. articulating the decisions behind it is another. i want to close that gap for myself.

most of what i'll write about lives in the space between systems programming and infrastructure. linux internals, networking stacks, the kind of low-level stuff that makes everything else possible. occasionally i'll write about whatever rabbit hole i've fallen into that week.

i'm not going to explain what a variable is. i'm going to assume you know your way around a terminal and go from there. if something i write helps you debug a problem at 2am, that's a win.

no schedule, no promises on cadence. just writing when there's something worth writing about.

let's go.