After years of thinking "I should write about this", I finally set up a blog section on my site.

The goal is simple: write about things I actually work with — distributed systems, backend architecture, developer tooling, and the occasional deep dive into something that surprised me. No tutorials for the sake of tutorials. Just notes from the trenches.

Why now?

I've been noticing that writing forces a level of clarity that thinking alone doesn't. When you try to explain something precisely, the gaps show up fast. That's useful.

Also, I've been integrating AI-assisted coding tools heavily into my workflow lately, and I want a place to document what actually works and what doesn't — beyond the marketing copy.

What to expect

Short, technical posts. Probably irregular cadence. No newsletter, no tracking, no dark patterns.

If something is useful to you, great. If not, that's fine too.

~$ _