Do one thing well — the Unix idea behind BenchKit

"Do one thing and do it well" is the core of the Unix philosophy, summarized by Doug McIlroy at Bell Labs in the 1970s: write programs that each do a single job, and make them work together. BenchKit applies that half-century-old idea to consumer web tools — each tool does one job completely, instead of one app trying to do everything and doing most of it poorly.

Where "do one thing well" comes from

In 1978, Doug McIlroy — the inventor of the Unix pipe — distilled the Unix philosophy into a few lines, the first being: "Make each program do one thing well." The insight was that small programs with sharp boundaries are easier to understand, easier to trust, and easier to combine than one large program that tries to anticipate every need. Decades of software history have kept proving it right.

Why it still holds for web tools

The principle transfers cleanly from command-line programs to the tools you open in a browser. A tool scoped to one job can be understood at a glance, loads fast because there's little to load, and rarely needs an account because a bounded task seldom needs your identity. An app that tries to do ten things has ten surfaces to learn, ten things to load, and a strong incentive to wrap it all in a login. Focus is still the feature — which is the practical argument in why single-purpose tools beat all-in-one apps.

What it looks like in practice

Applied honestly, "do one thing well" means each tool owns a single problem end to end and refuses the rest. It collects event photos, or it drills assessment games — and everything outside that boundary is deliberately left out, not half-built. The discipline is in what you say no to. That refusal is what keeps a tool sharp, and it's why I build small tools one at a time rather than one big app.

The honest limit

The Unix idea came with a second half that's harder to reproduce: those small programs composed through pipes, so ten focused tools could chain into one workflow. Consumer web tools don't compose that neatly — you can't pipe one browser tool into the next, so a kit of separate tools asks you to switch between them by hand. That's the real trade for keeping each one simple and account-free, and it's usually worth it for the narrow, occasional jobs these tools are built for.

Frequently asked questions

What is the Unix philosophy of "do one thing well"? It's a software design principle from Unix, summarized by Doug McIlroy in 1978: make each program do one thing well, and make programs work together. The idea is that small, sharply-scoped programs are easier to understand, trust, and combine than one large program that tries to do everything.

Does "do one thing well" still apply to modern apps? Yes for the tool's design, partly for composition. A single-purpose tool is still faster, clearer and more trustworthy than a bloated one. The part that transfers less cleanly is chaining tools together — browser tools don't pipe into each other the way Unix programs do.

How does BenchKit use this idea? Each BenchKit tool does one job completely and leaves everything else out, rather than being part of one app that does many things poorly. It's the Unix "do one thing well" principle applied to free, account-free web tools.