We build software products.

Writing software and running a product are different jobs. Code is finished when it works; a product is finished when someone can find it, understand it in seconds, install it without help, and still rely on it after an update. We plan for the second one, which makes a release a starting point rather than a finish line.

Every feature is paid for long after it ships — in support, in bugs, and in the time it takes anyone to understand the thing afterwards. We would rather release something narrow that works completely than something broad that works approximately. When we turn an idea down it is usually a good idea that belongs in a different product.

Most of a product's life is maintenance, so we write for whoever has to change it later — which is usually us. That means clear structure, one place for each decision, and no clever shortcut that saves an hour now and costs a day in a year. This site is built that way too: its visual values live in a single file, its content is validated before it can ship, and its architecture is written down rather than remembered.

Software is used by people who never asked to become experts in it. We design for the ordinary case before the impressive one: readable type, full keyboard access, both languages treated equally, and nothing that needs a fast connection to be useful. Accessibility and performance are requirements we check against, not polish applied at the end.