So this time, public.

I don't know what kind of engineer I'll be in five years. Genuinely don't. I find myself interested in too many things at once, how bytes move across a network, why some interfaces feel obvious without being explained, what separates a system that holds from one that crashes at 3am. People say I'll specialize eventually. Maybe. Right now the curiosity feels more honest than a job title would, so I'm following it.

This blog is where I think out loud while that's still happening.

Lately, I've been quite interested in Go. I came to me as another language, another syntax to memorize. What stopped me was the concurrency model. Goroutines aren't just cheap threads. The language is making an argument: stop managing execution, start thinking about communication. That inversion sat with me for a few days before it clicked. I'll probably write a lot about it.

This blog is closer to a journal where the entries happen to involve compilers and the occasional crisis of confidence that nobody in tech talks about honestly enough. I want to get better, at building things that hold, at understanding the layers I depend on, at writing clearly enough that future-me can read this without cringing too hard.

If something here is useful, good. If it just makes you feel less alone in not knowing something, that works too.