There is a class of software that was never meant to scale. It was made for one person, or for two, or for the small room of people who already understood the joke. It has a readme written in a hurry and a license copied from an older project. It does one thing, it does it in an odd way, and it does not apologise for either. I have been making this kind of software for about seven years now, and I have started to believe that it matters — not despite its smallness, but because of it.

The current internet has a very strong opinion about what a tool should look like. It should have a landing page with gradient hero copy. It should have a free tier and a paid tier and an enterprise tier. It should have a roadmap pinned to the top of its repository, a Discord invite, and an ambient anxiety about growth. None of this is wrong, exactly. But it describes only one shape of making, and I suspect it has begun to edit out all the others.

A tool for one is not a failed product. It is a finished sentence — spoken clearly in a small room, and left on the shelf in case someone wants to read it.

My own workshop is full of these sentences. A player plugin that lets me finish a show on the commute. A macOS menu-bar monitor that shows the real wattage of my laptop, because the built-in one kept lying to me. A Chrome extension that clusters my tabs with a local model, because my browser is a library and I am a bad librarian. None of these were built to be products. Most of them will never be. They are, to borrow a phrase from letterpress, job printing — small private editions, printed once, for the people actually in the room.

What I have learned, making them, is that the constraint of the tiny audience is generous. You can choose the odd keyboard shortcut. You can write error messages that sound like you. You can refuse to track anything, refuse to ask for an email, refuse to explain. You can, in other words, make something that feels like a letter rather than an announcement. And sometimes — not always — a letter travels further than an announcement, because it is warm to the touch.

This weekly is a letter of the same kind. I will file it when I have something to say and not when the calendar insists. I will use the word quiet more than is strictly fashionable. And I will continue to publish code into the forest, in case someone is walking there.