Brokentooth.io / About

09About

Why I build my own tools, and where all the pieces ended up.

I've always had a hard time leaving things alone. If something almost works the way I want, I want to get inside it and change it. A keyboard, a piece of software, an entire workflow. I have a very particular idea of how I want my tools to behave.

AI has made it possible to take that impulse considerably further than I could before. I can fork something, figure out how it works, and start making it my own.

Unfortunately, making one thing usually requires making another thing first. That requires fixing something else, which introduces several new dependencies, all of which apparently have their own opinions about how I should be doing things.

I own the whole stack now, but I can't even remember what I was trying to build to begin with. Can someone remind me?

Anyway, Brokentooth is where I'm keeping the results. The software, the machines, the unfinished ideas, the mistakes, and the things I've learned trying to make them work.

Some of this stuff is useful. Some is probably useful only to me. I'm not especially bothered by that. I like building it.

And somewhere along the way, this sprawling collection of inherited machines and heavily modified software has become a little space of my own.

What's here

Projects covers things with actual repositories and implementation history: OmniBoard, SessionMunch, Soma, ScreenSense and the watch work. A project page explains what something is for and where it stands. Related notes have room for the attempts, failures and details that would make an overview unreadable.

Machines records the computers involved and how their jobs change. Models follows speech, typing and other model experiments. Automation deals with the connections between tools, including the parts that need supervision despite being called automatic.

There is also room for visual work and writing. Practical utility is not the only reason to make something; it is simply worth being honest about which reason applies.

Colophon

The site is built from Markdown into static pages with a small Node-based generator. The interactive molar has a fallback for browsers without WebGL, so reading the site does not depend on the effect running.