Reading Notes for Linux/Unix design ideas

When I first got to know Erlang, I felt like a weird method named. When I wrote shell scripts, I suddenly realized that all the original sources were under "Linux/Unix design ideas", which is my reading notes, according to my own understanding, I reorganized: Reading Notes

1. Build a prototype as soon as possible to find a 90% solution. Run the solution first.
2. Keep the program small and do one thing at a time
3. Strengthen and expand the original software on the shoulders of giants
4. Sum of parts greater than total
5. There is often a trade-off between high efficiency and portability
6. Layered thinking

 

1. Interactive interfaces often make us farther away from the nature of the problem
2. Automation as much as possible
3. Make every program a filter. The common feature of all programs is to modify data without creating data.
4. Use lowercase letters and keep them short

However, if the text in the book is similar to the following, please check and judge it by yourself:

Maybe we should mention that Volkswagen once launched a successful automobile marketing campaign around the concept of "small is beautiful" and sold millions of cars; or think about the example of sun, a mainstream UNIX vendor. Its business strategy is based on the idea of "bringing the best fist product to all resources", or in other words, that is, the idea of "only do one thing well. So, are people interested in handheld computers, wireless network access, and handheld Videos related to portability? For the operating system, the gorgeous graphic interface has no significance unless it can provide users with the required functions. In other words, the content is king. People flock to the Internet and the World Wide Web to get text content.

 

References:

[1] how to identify the fire of thinking)

[2] how to identify the fire of thinking)

[3] how to identify the fire of thinking)

[4] How to become a free thinker