philosophy on developing software
Wikipedia
en.wikipedia.org › wiki › Unix_philosophy
Unix philosophy - Wikipedia
2 weeks ago - Later, in 1994, it was summarized with the explicit name "The Unix philosophy" by Peter H. Salus, who credited it to McIlroy: Write programs that do one thing and do it well.
Harvard
cscie2x.dce.harvard.edu › hw › ch01s06.html
Basics of the Unix Philosophy
Doug McIlroy, the inventor of Unix pipes and one of the founders of the Unix tradition, had this to say at the time [McIlroy78]: (i) Make each program do one thing well.
How does the Unix Philosophy matter in modern times?
It looks like you've majorly misunderstood what "do one thing well" means. Multi-tasking is a totally different concept in computation. In fact Unix machines were some of the first to do process scheduling and therefore "multi-tasking". For example, this shows all lines from this file, but only unique ones and sorted: cat file1 | uniq | sort I'm confident that "sort" does one thing and does it well. I'm not worried that I've mistakenly used a slow or broken "sort" utility. Each of these three programs do its thing well. I could also launch many threads or processes to run that command multiple times at the same time. That's a different concept. More on reddit.com
Doing One Thing, Well: The UNIX Philosophy
The UNIX philosophy is: parse some ambiguous text format, validated on three or four test cases that work in your environment; then do something well with it, provided there is no overflow of integers, buffers, token sizes, line lengths or such; then spit out another ambiguous text format for the next tool in the pipeline. More on reddit.com
The Unix philosophy is often recited as "do one thing, and do it well". This does one thing, but doesn't do it well at all.
What do you mean my software is bare bones, featureless and non-modifiable? I'm following the OONIX philosophy bro. More on reddit.com
"The Unix Philosophy" says create small functions that do one thing well. Is this code Unix-y?
Unix philosophy says write small applications that solve single task. So they can be united with pipes. Also they have the same input/output format - text. More on reddit.com
Does the Unix philosophy apply to Python or Go programs, or only to shell?
It applies to any program in any language. The interface requirements - stdin/stdout, meaningful exit codes, text or ndjson output, no unnecessary output on success - are language-independent. A Go binary that reads stdin and writes CSV to stdout is more Unix-philosophy-compliant than a shell script that requires a running database to function.
myunix.org
myunix.org › home › guides › unix philosophy explained: do one thing well
Unix Philosophy Explained: Do One Thing Well | MyUnix | MyUnix.org
What is the difference between doing one thing and being too minimal to be useful?
`sort` does one thing but has 40+ flags covering every legitimate sort use case. Depth within a single responsibility is not a violation. The violation is breadth - adding features that belong to a different conceptual domain. `sort --send-email` would be a violation. `sort --parallel` is not.
myunix.org
myunix.org › home › guides › unix philosophy explained: do one thing well
Unix Philosophy Explained: Do One Thing Well | MyUnix | MyUnix.org
Is the Unix philosophy still relevant for containerized and cloud-native environments?
Yes, and the container model is a direct application of it. Each container does one thing (run one service), communicates through standard interfaces (HTTP, TCP), and composes with other containers through defined protocols. Docker's `CMD` that runs a single foreground process is the container-level expression of the philosophy. Where cloud-native systems fail the philosophy is when a single container image bundles an application server, a cron runner, a metrics agent, and a log shipper.
myunix.org
myunix.org › home › guides › unix philosophy explained: do one thing well
Unix Philosophy Explained: Do One Thing Well | MyUnix | MyUnix.org
Reddit
reddit.com › r/linux › how does the unix philosophy matter in modern times?
r/linux on Reddit: How does the Unix Philosophy matter in modern times?
April 4, 2021 -
The Unix philosophy states that a program 'should do one thing and do it well'. This may have worked in the 1970s and 1980s, but in the modern era, where even the hardware does multiple jobs at a time, how does this matter? People want multi-tasking in their machines, and according to them it increases the efficiency. Why shouldn't software be able to multiple tasks?
Wouldn't it be better that a piece of software can do many operations, rather than one, while doing them all well?
Or, am I getting the whole idea of the Unix philosophy wrong?
Top answer 1 of 22
88
It looks like you've majorly misunderstood what "do one thing well" means. Multi-tasking is a totally different concept in computation. In fact Unix machines were some of the first to do process scheduling and therefore "multi-tasking". For example, this shows all lines from this file, but only unique ones and sorted: cat file1 | uniq | sort I'm confident that "sort" does one thing and does it well. I'm not worried that I've mistakenly used a slow or broken "sort" utility. Each of these three programs do its thing well. I could also launch many threads or processes to run that command multiple times at the same time. That's a different concept.
2 of 22
33
i mean, complex software is built with a bunch of specialized little programs that do one thing and do it well...
Author: Christian Mayer
Published: 2022
Pages: 176
Linuxtopia
linuxtopia.org › online_books › programming_books › art_of_unix_programming › ch01s06.html
Unix Programming - Basics of the Unix Philosophy
The ‘Unix philosophy’ originated with Ken Thompson's early meditations on how to design a small but capable operating system with a clean service interface. It grew as the Unix culture learned things about how to get maximum leverage out of Thompson's design.
LINFO
linfo.org › unix_philosophy.html
Unix philosophy description by The Linux Information Project (LINFO)
The Unix philosophy lies at the core of not only the original UNIX as developed by Ken Thompson at Bell Labs from 1969 but also of its numerous direct descendants and clones, including Solaris, the BSDs1 and Linux. It has made them, collectively referred to as Unix-like operating systems, into ...
John D. Cook
johndcook.com › blog › 2010 › 06 › 30 › where-the-unix-philosophy-breaks-down
Where the Unix philosophy breaks down
September 30, 2022 - Unix philosophy says a program should do only one thing and do it well. Solve problems by sewing together a sequence of small, specialized programs.
Finxter
blog.finxter.com › the-unix-philosophy
The Art of Clean Code — 14 Unix Principles – Be on the Right Side of Change
January 15, 2024 - “This is the Unix philosophy: 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.
Vivian Voss
vivianvoss.net › blog › the-unix-philosophy
The Philosophy — Vivian Voss
April 6, 2026 - McIlroy (1978): "Make each program do one thing well." Pike (1984): "The power comes from the relationships among programs." Ritchie: "UNIX is simple, but you have to be a genius to understand the simplicity."
The Infinite Unknown
jaredwatkins.com › research › software-philosophy › unix-philosophy
The Unix Philosophy - The Infinite Unknown
June 29, 2026 - Mike Gancarz of DEC’s Unix Engineering Group published a related formulation in 1994, summarizing Unix philosophy as nine tenets: small is beautiful; make each program do one thing well; build a prototype as soon as possible; choose portability over efficiency; store data in flat text files; ...