Unix philosophy
From Maths
Stub grade: C
This page is a stub
This page is a stub, so it contains little or minimal information and is on a to-do list for being expanded.The message provided is:
I link to this so much it'd actually be good to have my own version. This is taken from the OLD wiki page here which I STILL link to! Eric S. Raymond was/is one of my heroes but I did loose a tiny bit of awe/respect when I saw him trolling on the GCC mailing list once!
Eric S. Raymond
- Rule of Modularity[1] - write simple parts connected by clean interfaces
- Rule of Clarity[1] - Clarity is better than cleverness
- Rule of Composition[1] - Design programs to be connected to other programs
- Rule of Separation[1] - Separate policy from mechanism, separate interface from engines
- Rule of Simplicity[1] - Design for simplicity; add complexity only when you must
- Rule of Parsimony[1] - Write a big program only when it is clear by demonstration that nothing else will do
- Rule of Transparency[1] - Design for visibility to make inspection and debugging easier
- Rule of Robustness[1] - Robustness is the child of transparency and simplicity
- Rule of Representation[1] - Fold knowledge into data so program logic can be stupid and robust
- Rule of Least Surprise[1] - In interface design, always do the least surprising thing
- Rule of Silence[1] - When a program has nothing surprising to say it should say nothing
- Rule of Repair[1] - When you must fail, do so noisily and as soon as possible
- Rule of Economy[1] - Programmer time is expensive, conserve it in preference to machine time
- Rule of Generation[1] - Avoid hand-hacking; write programs to write programs when you can
- Rule of Optimisation[1] - Prototype before polishing. Get it working before you optimise it
- Rule of Diversity[1] - Distrust all claims for "one true way"
- Rule of Extensibility[1] - Design for the future, because it will be here sooner than you think
