I wear many hats. I write to figure out which one fits.

I build software — backends, frontends, the infrastructure in between, and sometimes the product strategy that decides what gets built at all. I care about the parts most engineers don't bill time for: what the error message sounds like, whether the abstraction leaks in the wrong place, and if the thing we shipped is actually the thing people needed.

I've learned that the best engineers aren't the ones who know the most tools. They're the ones who can see the system clearly enough to know which tool to reach for, and when to build something new instead.

I write long form because short takes are for opinions. Long form is for figuring out what you actually think. If I can't write it out completely, I probably don't understand it yet.

The topics here don't have a through-line beyond my own attention span: software architecture, design tradeoffs, mathematics, music theory, complexity. What they share is that I thought about them long enough to have something to say.