软件设计十七法则
来源:互联网 发布:ubuntu不显示wifi 编辑:程序博客网 时间:2024/04/28 17:36
(摘自《The Art of UNIX Programming》, Eric S. Raymond ,2004.5)
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 with other programs.
4. Rule of Separation: 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 when it 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 simplicity.
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 least surprising thing.
11. Rule of Silence: When a program has nothing surprising to say, it should say nothing.
12. Rule of Repair: Repair what you can -- but when you must fail, fail noisily and as soon as possible.
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 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.
All the philosophy really boils down to one iron law, the hallowed 'KISS principle' of master engineers everywhere:
K.I.S.S. Keep It Simple, Stupid!
原本想翻译一下的,后来发觉好难翻啊,还是原汁原味比较好……
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 with other programs.
4. Rule of Separation: 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 when it 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 simplicity.
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 least surprising thing.
11. Rule of Silence: When a program has nothing surprising to say, it should say nothing.
12. Rule of Repair: Repair what you can -- but when you must fail, fail noisily and as soon as possible.
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 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.
All the philosophy really boils down to one iron law, the hallowed 'KISS principle' of master engineers everywhere:
K.I.S.S. Keep It Simple, Stupid!
原本想翻译一下的,后来发觉好难翻啊,还是原汁原味比较好……
- 软件设计十七法则
- 软件设计10个基本法则
- 软件设计原则----迪米特法则(LoD)
- 软件设计原则----迪米特法则(LoD) .
- 软件设计模式之迪米特法则(Darren)
- 轻量化软件设计五大法则
- 软件设计原则之笛米特法则【Principle of Least Knowledge】
- 80/20法则在软件设计中可行吗?
- 纯干货!轻量化软件设计五大法则
- 软件设计原则(六)迪米特法则 -Law of Demeter
- 拿破仑·希尔的十七条黄金法则
- 软件设计
- 软件设计
- 软件设计
- 软件设计
- 软件设计
- 软件设计
- 软件设计
- ASP.NET零起点教程
- XSLT对结果的分组(包括1.0和2.0新的功能)
- 《Here I am》--小马精灵的生活主题曲
- 杂谈
- 上面这些是每天对房间的预约(已经预定)
- 软件设计十七法则
- jakarta commons-net ftp的例子
- JS结合数据库的二级联动菜单
- ACE-IPC(TCP)
- ACE-IPC(UDP)
- Excel中巧用函数对文本型数值求和
- ACE-IPC(MULTICAST)
- csdn,我回来了
- 宿命论? 信不~~