About

I'm a software engineer based in New York. I work mostly on the infrastructure side of things — build systems, developer experience, the kind of plumbing that nobody notices until it breaks. I care a lot about making complex systems understandable, which probably explains why I also spend a lot of time thinking about writing and how knowledge moves between people.

I grew up reading everything I could find, which gave me a lot of half-formed opinions about a lot of topics and a deep suspicion of people who are too certain about things. I find most interesting problems are interesting precisely because they resist clean answers.

Things I think about more than is probably reasonable: how people actually learn things versus how they think they learn things, what makes a piece of writing feel true, the aesthetics of well-designed tools, why some places feel like places and others don't.

What this site is

This is a digital garden — a term I find a little precious but don't have a better one for. It's where I put writing that I want to keep, organized by what the notes are about rather than when I wrote them. Some of it is finished; a lot of it isn't. That's deliberate.

I started it because I kept writing things in notebooks and never going back to them, and I wanted somewhere they'd be slightly more alive than that. It's not a blog and it's not a portfolio. It's closer to a working space that happens to be public.

What I'm not

I don't have a newsletter, a course, or a community. I'm not trying to build an audience. If you find something here useful, that's genuinely nice to hear, but it's not the point.