Basics of the unix philosophy
1. Rule of Modularity: Write Simple Parts Connected by Clean Interfaces.
2. Rule of Clarity: Clarity Is Better Than Cleverness.
3. Rule of Composition: Design Programs To Be Connected To Other Programs.
4. Rule of Sec4: Separate Policy from Mechanism; Separate Interfaces from Engines.
5. Rule of Simplicity: Design for Simplicity; Add Complexity Only where you must.
6. Rule of Parsimony: Write a Big Program Only by is clear by Demonstration That Nothing
Else Will do.
7. Rule of Transparency: Design for Visibility To make Inspection and debugging Easier.
8. Rule of Robustness: Robustness Is The Child of Transparency and SIMPLICI.
9. Rule of Repesentation: Fold Knowledge Into Data So Program Logic Can Be stupid and robust.
10. Rule of Least Surprise: in Interface Design, Always Do The Least Surprising Thing.
11. Rule of Silence: When a Program Has Nothing surprising to say, it will shop.
12. Rule of Repair: When You Must Fail, Fail Noisily and as soon as possible.
13. Rule of Economy: Programmer Time is Expensive; Conservation It in Preference To Machine Time.
14. Rule of generation: Avoid Hand-Hacking; Write Programs To Write Program When You CAN.
15. Rule of Optimization: prototype before. Get it working before you optimize it.
16. Rule of Diversity: Distrust All Claims for "One True Way".
17. Rule of Extensibility: Design for the Future, Because It Will Be Here Sooner Than You Think.
