Why I'm starting this blog

I’ve spent the last while building things without writing much down about how any of it actually got built. There’s TraceBloom, a synthetic clinical-data pipeline I worked on at JUNITEC, an AR education platform for the Gulbenkian Museum, and the 80+ Linux servers I help keep running at RNL. All of it happened, but none of it got written up.

That’s what this blog is for. A few things I want to write about:

• What I’m learning, as I go. New tools, patterns, and the occasional debugging story that took way too long to figure out.
• What I’m building, in side projects and at work, along with the trade-offs behind the decisions I made.
• The overlap between product and engineering, since that’s where I spend most of my time and it rarely shows up in a commit diff.

No fixed schedule and no pressure to make every post perfect. I’ll write when I have something worth saying.

If you want to follow along, there’s an RSS feed. Otherwise, see you in the next post.