The Unix Philosophy
Ken Thompson, Dennis Ritchie & Doug McIlroy · 1978
"Unix won not by features but by composition — small tools that do one thing well, speak in text streams, and compose via pipes, so new capabilities emerge from combining old parts rather than rewriting."
Doug McIlroy's foreword to the 1978 Bell System Technical Journal issue on Unix compressed a decade of Thompson and Ritchie's practice into a three-line manifesto: write programs that do one thing well, write programs to work together, and handle text streams as a universal interface.
Pipes (' | ') and text made composition the default: grep, sed, awk, and later curl and jq can be strung to do what no single tool was designed for, without central coordination. The mechanism is constraints as capability — by refusing to build a monolith, Unix forced an ecosystem of interoperable parts, which is why a 1970s terminal still feels productive in 2026. Modern echoes: microservices, LoRA adapters, and the Unix-like 'small sharp tools' inside Linear's own architecture.
What does the Unix philosophy claim makes a system more evolvable than a feature-rich monolith?
Read more about the topic
The explanation above is written with AI assistance. These are the originals — go to them to check it.
- The UNIX Time-Sharing System (Ritchie & Thompson, 1978) overviewDennis Ritchie & Ken Thompson / Wikipedia
Moore's Law & the Exponential
"Moore observed in 1965 that the number of components per chip was doubling every year (a rate he revised to every two years in 1975) — an exponential that held long enough to make the future systematically cheaper to compute than the present, and to make exponential thinking the required default for tech strategy."