The Rules of Unix
Last Fall, Eric Raymond published “The Art of Unix Programming” – a book I’m going to have to buy, since it’s 500 pages are just too much for the screen. In the first chapter, he lists the rules that make up the Unix philosophy, and reading through them, I was struck by their application to what I do – IA, UX, design, et al.
Rule 10 is interaction design. Rule 14 is why we use templates to spit out HTML. Rule 4 is how CSS works. Rule 13 is my resolution for this year, restated. Rule 16 is why we started this company.
- Rule of Modularity: Write simple parts connected by clean interfaces.
- Rule of Clarity: Clarity is better than cleverness.
- Rule of Composition: Design programs to be connected to other programs.
- Rule of Separation: Separate policy from mechanism; separate interfaces from engines.
- Rule of Simplicity: Design for simplicity; add complexity only where you must.
- Rule of Parsimony: Write a big program only when it is clear by demonstration that nothing else will do.
- Rule of Transparency: Design for visibility to make inspection a nd debugging easier.
- Rule of Robustness: Robustness is the child of transparency and simplicity.
- Rule of Representation: Fold knowledge into data so program logic can be stupid and robust.
- Rule of Least Surprise: In interface design, always do the least surprising thing.
- Rule of Silence: When a program has nothing surprising to say, it should say nothing.
- Rule of Repair: When you must fail, fail noisily and as soon as possible.
- Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.
- Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.
- Rule of Optimization: Prototype before polishing. Get it working before you optimize it.
- Rule of Diversity: Distrust all claims for “one true way”.
- Rule of Extensibility: Design for the future, because it will be here sooner than you think.
He elaborates on them in the rest of the chapter. The whole book is <a href=””“>here</a>.