Unix Zen

• Rule of Modularity: Write simple parts connected by clean interfaces.


• Rule of Composition: Design programs to be connected to other programs.


• Rule of Clarity: Clarity is better than cleverness.


• Rule of Simplicity: Design for simplicity; add complexity only where you must.


• Rule of Transparency: Design for visibility to make inspection and debugging easier.


• Rule of Robustness: Robustness is the child of transparency and simplicity.


• Rule of Least Surprise: In interface design, always do the least surprising thing.


• 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 Representation: Fold knowledge into data so program logic can be stupid and robust.


• Rule of Separation: Separate policy from mechanism; separate interfaces from engines.


• 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.

And shame on me, for reading Raymond. taken from here