The Art of UNIX Programming的笔记(3)

按有用程度 按页码先后 最新笔记

• 

  multiprogramming

  oldfrau

  用多进程的方式，使问题局部化，进而间接的降低了系统整体的复杂度。 (更多)

  用多进程的方式，使问题局部化，进而间接的降低了系统整体的复杂度。 (收起)

  2012-04-08 02:34:34   回应

  收藏

  推荐
• 

  1.6 Basics of the Unix Philosophy

  rns

  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 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:... (更多)

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

  (收起)

  2012-01-15 00:04:01   回应

  收藏

  推荐
• 

  第47页

  yakergong (因为懂得，所以慈悲)

  The only way to write complex software that won't fall on its face is to hold its global complexity down — to build it out of simple parts connected by well-defined interfaces, so that most problems are local and you can have some hope of upgrading a part without breaking the whole. (更多)

  The only way to write complex software that won't fall on its face is to hold its global complexity down — to build it out of simple parts connected by well-defined interfaces, so that most problems are local and you can have some hope of upgrading a part without breaking the whole.

  (收起)

  2011-06-08 14:18:34   回应

  收藏

  推荐