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. It absorbed lessons from many sources along the way. The Unix philosophy is not a formal design method. It wasn't handed down from the high fastnesses of theoretical computer science as a way to produce theoretically perfect software. Nor is it that perennial executive's mirage, some way to magically extract innovative but reliable software on too short a deadline from unmotivated, badly managed, and underpaid programmers. The Unix philosophy (like successful folk traditions in other engineering disciplines) is bottom-up, not top-down. It is pragmatic and grounded in experience. It is not to be found in official methods and standards, but rather in the implicit half-reflexive knowledge, the expertise that the Unix culture transmit
Basics of the Unix Philosophy Basics of the Unix Philosophy Prev � Chapter�1.�Philosophy � Next 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. It absorbed lessons from many sources along the way. The Unix philosophy is not a formal design method. It wasn't handed down from the high fastnesses of theoretical computer science as a way to produce
Explore this link on the map →saved by
related reading
- Basics of the Unix Philosophycscie2x.dce.harvard.edu
- The UNIX-HATERS Handbookweb.mit.edu
- Rise of Worse Is Betterdreamsongs.com
- What Unix Gets Rightcatb.org
- Rise of Worse Is Betterdreamsongs.com
- Thing worth doingokigiveup.net
- The Anti-Mac User Interface (Don Gentner and Jakob Nielsen) - NN/Gnngroup.com
- Small, Sharp Tools — brandur.orgbrandur.org
- Michael Feathers - 10 Papers Every Developer Should Readmichaelfeathers.silvrback.com
- Ken Thompson - Wikipediaen.wikipedia.org
- On architecture, urban planning and software construction - Tomas Petricektomasp.net
- The Programmer's Paradox: Systems Thinkingtheprogrammersparadox.blogspot.com