Basic of the Unix Philosophy
来源:互联网 发布:移动一天都没网络信号 编辑:程序博客网 时间:2024/04/28 05:07
Rule of Modularity: Write simple parts connected by clean interface
Rule of Clarity: Clarity is better than cleverness
Rule of Composition: Design programs to be connected with other programs.
Rule of the 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 the transparency: Design for visibility to make inspection and debugging easier.
Rule of Robustness: Robustness is the child of transparency and simplicity.
Rule of Representation: Fold knoweledge 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: Repair what you can--but 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.
All these rules are from the book: The art of UNIX Programming, written by Eric S. Raymond.
Rule of Clarity: Clarity is better than cleverness
Rule of Composition: Design programs to be connected with other programs.
Rule of the 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 the transparency: Design for visibility to make inspection and debugging easier.
Rule of Robustness: Robustness is the child of transparency and simplicity.
Rule of Representation: Fold knoweledge 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: Repair what you can--but 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.
All these rules are from the book: The art of UNIX Programming, written by Eric S. Raymond.
- Basic of the Unix Philosophy
- Basics of the Unix Philosophy
- the UNIX Philosophy
- The UNIX Philosophy
- The Unix Philosophy
- The UNIX Philosophy
- The Philosophy of Scrum
- Linux and the Unix Philosophy
- Philosophy of the GNU Project
- The Philosophy of Computer Science
- 书籍推荐:《Linux and the Unix Philosophy》
- Linux and the Unix Philosophy Summary
- UNIX Philosophy
- Unix Philosophy
- 简单的哲学(The Philosophy of Simplicity)
- linux/unix 哲学概述 (Linux and the Unix Philosophy)
- Linux/Unix设计思想(Linux and the Unix Philosophy)
- [Not Solved] [Unix Philosophy] [The Art of Unix Programming] 怎样理解 "X致力于提供一套'机制, 而不是策略'" 的设计理念
- tomcat下调试jsp的常见问题(一)
- 安装Eclipse和Lomboz碰到的一些问题 (zz)
- jsp如何把图片和媒体文件存入oracle中
- 今儿竟然是万圣节
- 网络命令详解(转)
- Basic of the Unix Philosophy
- 关联作业和完成端口
- 学生校方法庭激辩:四川大学是不是名牌
- 在二区,学了一天
- Edit控件里没数据时CheckBox的窗口就设为不可用
- 一段找出URL的代码(C#)
- 刀兄写的IIS管理类(C#)
- 必须有默认值
- Integrating PayPal Payments (转)