Building differently · a stance, not a tour
Most software makes you pick: rigorous, or a pleasure to use. You don’t have to.
That’s the whole claim. It’s small, and it’s testable — and the test isn’t this page. It’s a shelf of free tools you can run in the next five minutes, with no account and no AI. Read the case, then go argue with the tools.
The default
The trade-off you were handed
Somewhere along the way, building software turned into a choice between two bad options. On one side, serious: heavy, framework-laden, joyless, the kind of thing that takes a week to set up before it does anything. On the other, a toy: cute, throwaway, fun for an afternoon and useless by Friday. The unspoken rule is that rigor and delight trade against each other — that if a thing is a pleasure to use, it’s probably not serious, and if it’s serious, it’s probably a slog.
And lately there’s a third assumption stacked on top: that “built with AI” means hype, lock-in, and a black box — that reaching for the new tools means handing over the part where you actually understand what you made.
The turn
Correctness is not the finish line
Here is the thing the trade-off gets wrong. A tool can be exactly, provably correct and still be dead — because if nobody wants to pick it up, its correctness doesn’t matter to anyone. Being right is necessary. It was never sufficient. Whether a person wants to engage with the thing is not a nicety you add at the end; it’s a load-bearing requirement, the same as the thing working at all.
Which means play isn’t the opposite of rigor. Play is how rigor survives contact with a person. The whimsy isn’t decoration painted over the serious part; it’s the part that gets the serious part used. Once you see it that way, the trade-off stops being a law of nature and starts looking like a habit nobody checked.
But a claim like that is cheap. Anyone can say “rigorous and delightful.” So don’t take it as an argument. Take it as tools.
The proof
The evidence is a shelf, not a pitch
Pulled out of a working system and given away: dozens of small tools. Each one is a single file. Each is MIT-licensed — read the source, run it, drop it into something you sell, no permission asked. None of them needs an AI to run, or an account, or a framework. And each one ships with its honest edge printed right on it — the limit, the thing it can’t do, stated plainly — because a tool that hides its edges is the opposite of a gift.
The trick that makes them more than a pile: they compose. The small sharp pieces snap together into bigger ones, which is how a handful of single-file tools does the kind of work you’d expect to need a whole framework for. That’s a craft idea, not an AI one — it’s as old as the command line.
If you’re wary of AI
You think “built with AI” means slop and lock-in. That’s a fair prior; a lot of it is. So here’s the test, and it’s built for exactly your suspicion: every tool on that shelf runs with no AI, no account, MIT, and its limits printed on it. Judge the tools, not the story behind them. You never have to touch AI to use a single one — and if they’re good, then the way of building that produced them is at least worth a look. The stance earns your attention by handing you something that works, first.
If you build with AI all day
You already know the failure mode: the black box — the thing that works right up until it doesn’t, and you can’t see why. Here’s the quiet part. The same property that lets a skeptic run these tools with no AI — single-file, dependency-free, limits stated, nothing hidden — is exactly what keeps AI-built work legible instead of opaque. Determinism and AI aren’t opposites here; the determinism is what makes the AI safe to lean on. Same tools, same system, both ways in.
The other side
What’s across the threshold
So this is the turn, if you take it: you can build things that are rigorous and a pleasure — and the way you prove it, to a stranger who owes you no benefit of the doubt, is to give the things away with their limits showing. Not a demo. Not a locked trial. The actual tool, the actual edge, in your hands, today.
Building differently was never really about which tools you reach for. It’s about what you refuse to trade away — the part where the person on the other end can see what you made, use it without asking, and hold you to what it claims. That’s the door. It opens the same whether you walk in refusing AI or fluent in it.
Go argue with the tools →
The whole shelf — dozens of free, single-file, MIT tools, each with its honest edge printed on it and the one command to run it. Nothing there needs an AI. Start with any card that looks useful.
Or read The Thesis for what the whole system claims, or The Developer’s Guide for how the pieces snap together.