金慶的專欄

Unix編程哲學(xué)

參考其它另外三個不同版本的翻譯：
* Imperfect C++中文版
* 心開天籟
* Unix編程哲學(xué)


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.

組合準則：設(shè)計可以相互連接的程序。

4.Rule of Separation:Separate policy form mechanism; separate interfaces from engines.

分離準則：策略同機制分離；接口同引擎分離

5.Rule of Simplicity: Design for simplicity; add complexity only where you must.

簡單性準則：設(shè)計要簡單，必要時才添加復(fù)雜性。

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 debug going easier.

透明性準則：設(shè)計要直白，使檢查和調(diào)試更易容。

8:Rules 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.

表示準則：數(shù)據(jù)體現(xiàn)知識，讓邏輯單純而健壯

10:Rule of  Least Surprise:In interface design, always do the least surprising thing.

最小驚奇準則：在接口設(shè)計中，避免出乎意料。

11:Rule of Silence: When a program has nothing surprising to say, it should say nothing.

沉默準則：如果程序沒有什么好說的，就應(yīng)該保持沉默。

12:Rule of Repair:When you must fail, fail nosily and as soon as possible.

修復(fù)準則：如果注定失敗，要盡早，要大聲。

13:Rule of Economy:Programmer time is expensive; conserve it in preference to machine time.

經(jīng)濟性準則：和機器的時間比較，程序員的時間是更寶貴的。

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.

優(yōu)化準則：打磨前先成型，優(yōu)化前先使它工作。

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.

擴展性準則：為未來設(shè)計，因為它來的比你想得早。

（轉(zhuǎn)載請注明來源于金慶的專欄）