Kimi Takemura



竹村

︎︎︎ info
︎︎︎ shop
︎︎︎ notes

︎︎︎ microsoft Learn
︎︎︎ Microsoft Azure
︎︎︎ Amazon web services

︎︎︎ projects
︎︎︎ sketchbooks

︎︎︎ site index
Unix Philosophy

The Unix philosophy emphasizes building simple, compact, clear, modular, and extensible code that can be easily maintained and repurposed by developers other than its creators.
  1. _Modularity:
    Write simple parts connected by clean interfaces.


  2. _Clarity:

    Clarity is better than cleverness.


  3. _Composition:

    Design programs to be connected to other programs.


  4. _Separation:

    Separate policy from mechanism; separate interfaces from engines.


  5. _Simplicity:

    Design for simplicity; add complexity only where you must.


  6. _Parsimony:

    Write a big program only when it is clear by demonstration that nothing else will do.


  7. _Transparency:

    Design for visibility to make inspection and debugging easier.


  8. _Robustness:

    Robustness is the child of transparency and simplicity.


  9. _Representation:

    Fold knowledge into data so program logic can be stupid and robust.


  10. _Least Surprise:

    In interface design, always do the least surprising thing.


  11. _Silence:

    When a program has nothing surprising to say, it should say nothing.


  12. _Repair:

    When you must fail, fail noisily and as soon as possible.


  13. _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. _Optimization:

    Prototype before polishing. Get it working before you optimize it.


  16. _Diversity:

    Distrust all claims for “one true way”.


  17. _Extensibility:

    Design for the future, because it will be here sooner than you think.