Proposed Term
Unix Philosophy
Context
A set of cultural norms and design principles for building modular, minimal, composable software, articulated by Doug McIlroy (Bell Labs) and embodied in Unix. McIlroy's canonical formulation: "Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface."
Later codified by Eric S. Raymond in The Art of Unix Programming as 17 rules (Modularity, Clarity, Composition, Separation, Simplicity, Parsimony, Transparency, Robustness, Representation, Least Surprise, Silence, Repair, Economy, Generation, Optimization, Diversity, Extensibility).
It is the oldest practical embodiment of Separation of Concerns (companion proposal #627) — "one tool, one job" — and a strong LLM anchor for the same reason: instructing a model to follow the Unix philosophy biases output toward small, single-purpose, composable units instead of a "do-everything" monolith.
Fits design-principles; relatives in the catalog: separation-of-concerns (proposed, #627), kiss-principle, dry, iosp, single-level-of-abstraction-principle, law-of-demeter, postels-law.
Sources: McIlroy et al., "UNIX Time-Sharing System: Foreword", Bell System Technical Journal 1978 · Eric S. Raymond, The Art of Unix Programming — http://www.catb.org/~esr/writings/taoup/html/
LLM Activation Test Result
Model: Claude (Opus 4.8)
Prompt: "What concepts do you associate with 'Unix Philosophy'?"
Response: "Do one thing and do it well"; small, sharp, composable tools piped together; text streams as the universal interface; modularity, simplicity, parsimony; KISS; "worse is better"; attributed to McIlroy / Thompson / Ritchie at Bell Labs and codified by Eric S. Raymond (17 rules). Practical ancestor of Separation of Concerns and the antithesis of the monolithic "do-everything" program. Rich, consistent, strongly attributable activation.
Pre-submission Checklist
Proposed Term
Unix Philosophy
Context
A set of cultural norms and design principles for building modular, minimal, composable software, articulated by Doug McIlroy (Bell Labs) and embodied in Unix. McIlroy's canonical formulation: "Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface."
Later codified by Eric S. Raymond in The Art of Unix Programming as 17 rules (Modularity, Clarity, Composition, Separation, Simplicity, Parsimony, Transparency, Robustness, Representation, Least Surprise, Silence, Repair, Economy, Generation, Optimization, Diversity, Extensibility).
It is the oldest practical embodiment of Separation of Concerns (companion proposal #627) — "one tool, one job" — and a strong LLM anchor for the same reason: instructing a model to follow the Unix philosophy biases output toward small, single-purpose, composable units instead of a "do-everything" monolith.
Fits design-principles; relatives in the catalog:
separation-of-concerns(proposed, #627),kiss-principle,dry,iosp,single-level-of-abstraction-principle,law-of-demeter,postels-law.Sources: McIlroy et al., "UNIX Time-Sharing System: Foreword", Bell System Technical Journal 1978 · Eric S. Raymond, The Art of Unix Programming — http://www.catb.org/~esr/writings/taoup/html/
LLM Activation Test Result
Model: Claude (Opus 4.8)
Prompt: "What concepts do you associate with 'Unix Philosophy'?"
Response: "Do one thing and do it well"; small, sharp, composable tools piped together; text streams as the universal interface; modularity, simplicity, parsimony; KISS; "worse is better"; attributed to McIlroy / Thompson / Ritchie at Bell Labs and codified by Eric S. Raymond (17 rules). Practical ancestor of Separation of Concerns and the antithesis of the monolithic "do-everything" program. Rich, consistent, strongly attributable activation.
Pre-submission Checklist