A millwright is a craftsperson who builds and maintains the machinery a mill runs on: the belts, the shafts, the mountings nobody inspects until the day they have to. It’s not glamorous work. Most of it is out of sight. When it holds, nobody thinks about it. When it fails, the whole floor stops. That’s the part of software we care about.
A quiet test for every feature
Before we ship anything, we ask one question: if this breaks on a Tuesday morning, what stops working? If the honest answer is “nothing much,” the feature is probably not worth the maintenance cost of having it. If the answer is “the whole day,” then the feature is load-bearing, and it needs to hold.
That framing kills the kind of speculative feature that sneaks in on the strength of sounding clever. And it raises the bar on the things that do ship, because we know in advance that we’re on the hook for their reliability.
What holding actually looks like
A load-bearing feature works on a patchy 4G connection in the back room of a salon. It’s obvious enough to use without a help article. It fails in ways the user can recover from without calling anyone. It doesn’t change shape between releases.
None of these show up on a marketing page. Which is a bit of the point. The parts of software that matter most to the people using it are usually the parts that photograph worst.
On the name
Naming is a form of promise. Calling the studio Millwright is a way of saying: this is the part of the building we’ve chosen to look after. If we ship something that isn’t load-bearing, we’ll feel the name before anyone else does.