Name: Anonymous 2017-07-22 1:12
1. Rule of Modularity: Write simple parts connected by pipes, sed, grep, and shell scripts.
2. Rule of Clarity: Clarity is better than cleverness.
3. Rule of Composition: Design programs to output text streams to other programs.
4. Rule of Separation: Separate policy from mechanism; separate interfaces from engines.
5. Rule of Simplicity: Design for simplicity; add error handling only where you must.
6. Rule of Parsimony: Write a big program only when it grew from a small program.
7. Rule of Transparency: Design for C programmers to make inspection and debugging easier.
8. Rule of Robustness: Robustness is the child of abort and stderr.
9. Rule of Representation: Fold knowledge into data so program logic can be stupid and robust.
10. Rule of Least Surprise: In interface design, always do the backwards compatible thing.
11. Rule of Silence: When a program has nothing surprising to say, it should say nothing.
12. Rule of Repair: When you must fail, abort and dump core.
13. Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.
14. Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.
15. Rule of Optimization: Prototype before polishing. Get it popular so you can get others to optimize it.
16. Rule of Diversity: Distrust all claims for “one true way” unless it's the Unix philosophy.
17. Rule of Extensibility: Design for the PDP-11, because the future will never come.
2. Rule of Clarity: Clarity is better than cleverness.
3. Rule of Composition: Design programs to output text streams to other programs.
4. Rule of Separation: Separate policy from mechanism; separate interfaces from engines.
5. Rule of Simplicity: Design for simplicity; add error handling only where you must.
6. Rule of Parsimony: Write a big program only when it grew from a small program.
7. Rule of Transparency: Design for C programmers to make inspection and debugging easier.
8. Rule of Robustness: Robustness is the child of abort and stderr.
9. Rule of Representation: Fold knowledge into data so program logic can be stupid and robust.
10. Rule of Least Surprise: In interface design, always do the backwards compatible thing.
11. Rule of Silence: When a program has nothing surprising to say, it should say nothing.
12. Rule of Repair: When you must fail, abort and dump core.
13. Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.
14. Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.
15. Rule of Optimization: Prototype before polishing. Get it popular so you can get others to optimize it.
16. Rule of Diversity: Distrust all claims for “one true way” unless it's the Unix philosophy.
17. Rule of Extensibility: Design for the PDP-11, because the future will never come.