Description: idea according to which one or standard to implement the functions. The same function can have different designs to achieve. With the increase in demand, the role of design can be reflected
Combined with "UNIX / LINUX design"
Guideline 1: Small immediate US
Rule 2: Let each program is only one thing to do
Guideline 3: rapid prototyping (a planned thing, for three years, found not finish users want, do first small, and then modify)
Guideline 4: abandon high efficiency and take portability (such as software is relatively inefficient, but he may be behind a hardware smoothed)
5 criteria: to store data in plain text (easy readability, poor readability stored binary)
Guideline 6: Take advantage of leverage software (software reuse, can abstract the abstract, to multiplex multiplex)
Guideline 7: Using shell scripts to increase leverage and portability
Guideline 8: Avoid mandatory user interface (linux only command line user interface accounts for a lot of memory)
Guideline 9: Let each program are called filters
Small Guidelines: allows users to customize the environment
Small guidelines: try to make the operating system kernel is small and lightweight
Small guidelines: Use lowercase letters and try to be brief
Small guidelines: silence is golden
Small guidelines: a whole greater than the sum of its parts
Small guidelines: seek 90% solution (only 90% of people to solve the problem, the remaining 10% do not like to use)
Demo: silence is golden + let each program called filter
For example, input terminal: ls, will output all the files and folders, ls in fact filter. He put the current folder and all the files to filter out files
You can also enter: ls | grep 'package'. Filter package containing a file name of the file in all files in ls
When the input ls | grep 'package1'. Nothing export, and that silence is golden. If you prompted no file on the problem