The golden Wisdom about open source

2. Good software works often originate from the individual needs of the developer.
4. Good programmers know what to write, and excellent programmers know what to rewrite (and reuse).
6. "Plan to throw away one, sooner or later you will." (Fred Brooks, "The Man-month myth", chapter 11th)
8. If you have the right attitude, interesting things will naturally find you.
10. When you are no longer interested in a program, your final responsibility is to hand it over to a competent stick-up person.
12. Treat your users as development collaborators, which is the most hassle---if you want to quickly improve code quality and effectively debug.
14. Early release, often published, listen to user feedback.

16. If there are enough beta testers and co-developers, almost all of the problems will appear quickly, and then naturally someone will solve them.

    Beta tests are "beta tests" and correspond to "alpha tests". For an upcoming software PRODUCT, Alpha testing refers to testing the product (Alpha version at this point) by the software company's internal testers to simulate a variety of user behaviors. Subsequent beta testing refers to a software company that organizes a variety of typical users to use in their daily work (the beta version of the product) and asks the user to report errors and anomalies. Finally, the software company modified the beta version of the error and improved.

18. A clever data structure with stupid code is much better than the reverse.

20. If you treat beta testers as the most precious resource, they will become your most valuable resource.
22. Second only to having a good idea is to identify good ideas from the user, sometimes the latter will be better.
24. Often, the most groundbreaking and innovative solutions come from the realization that you are wrong about the basic idea of a problem.
26. "The perfection of design is not that nothing can be added, but nothing can be reduced." ”
28. Any tool should have expected functionality, but a great tool can bring you unexpected functionality.
30. When writing gateway-class software, do not disturb the data stream as much as possible, and never throw away information unless the receiver forces you to do so.

32. When your language is far from complete (turing-complete), grammatical sugars can benefit you a lot.

    Grammatical sugars (syntactic Sugar, or syntactic icing) is a term invented by the British computer scientist Peter J.landin, which refers to the addition of some component to the computer language that does not affect the language function, but makes it easier to use, with the aim of enhancing the readability of the code and avoiding the chance of error.

34. The security of a system depends only on the secrets it has. Beware of false secrets.

36. To solve an interesting problem, first find a problem that interests you.
38. If the development coordinator has a good communication medium, at least like the internet, and knows how to lead without coercion, then the cooperation of many people must be stronger than individual combat.

From "The Cathedral and the Bazaar"

The golden Wisdom about open source