Starting a blog

I studied computer science and I'm curious about most of tech. Right now a lot of my work is building data platforms: moving data from where it happens to where it can be understood, into tables people trust. Along the way I collect small lessons that never quite fit into a commit message. This is where they go.

No grand plan. Just notes I'd have wanted to read earlier: the failure that took an afternoon to diagnose, the design decision that aged well, the tool that was quietly better than its reputation.

How this is built

The whole site is a handful of static files. There is no framework, no build step, no analytics, and nothing to track you. A page is HTML; the styling lives in one small stylesheet; a few lines of JavaScript remember whether you prefer light or dark.

Writing a new post means copying a template and filling in the prose. That's deliberate. The friction of a build pipeline is exactly the friction that keeps a blog empty.

The best system for writing is the one that lets you write without thinking about the system.

What to expect

• Streaming systems: Kafka, Flink, change data capture, and the sharp edges between them.
• Lakehouse platforms: table formats, layout, and keeping query cost honest.
• The unglamorous parts: backfills, schema evolution, and the quiet art of not losing data.

If any of that is your world too, welcome. If you want to talk shop, the links at the bottom of every page reach me.