1, the early release of benefits is often released “enough eyeballs, all bugs are shallow grasp” linuz law
2, in theory, because the debugger repeated loss of efficiency resulting from acting in the Linux “the practice of the world never seems to be a problem.
3, if there may be a big bug, Linux “kernel version number to allow potential customers to choose and older stable version, or take risks in order to bug the edge version of the latest features.
4, if the most valuable resources for you to treat your beta testers, they will become the most valuable resources in response.
5, in writing gateway software of any time spent doing something as much as possible not to interfere with the data stream – unless the user forces you, never throw away any information!
6, although the Internet is the cheapest Linux model evolved out of the necessary conditions, I think he was not a sufficient condition. Another key factor is the kind of leadership style and the establishment of a cooperative system – allows developers to attract partners, in this medium to get maximum benefits.
7, is how to think. I know of a good manageress seems that software project management has five functions:
â— clear objectives and maintain the efforts of everyone in the same direction
â— to monitor and ensure that key details are not to be missed
â— mobilize people to do boring but necessary job coolies
â— Allocation of personnel to achieve the best productivity
â— Monitoring the resources needed to continue the project
8, it is generally in a range of difficulty of the task in an appropriate time to have fun; not too simple As for boring, not too hard a bad implementation. A happy programmer is neither wasted nor were the goals and annoying error on friction and overwhelmed by the people. Fun leading to efficiency.
I read the above process, the key words that meaningful sentences.
Is the book, actually more like a blog in order. Before seen a “out of the software workshop,” this book is written by senior members of CSDN a style with the “Cathedral and the Bazaar” almost, content and organization than the “Cathedral and the Bazaar” good.
Overall, I think, after watching the whole book, more disappointed. I do not know enough themselves gulping or understanding, feeling of general nature, than the “out of the software workshop,” even worse (though in different content, but similar in style).
“The Cathedral and the Bazaar” of what is to briefly talk about the Cathedral, what is the market, and then he began to develop a fetchmail as an example to illustrate how the market works.
Simply put, the market, generally for the improvement of existing software. In general, the original author of this software, the use of a fixed population (all those open source enthusiasts) and some development defenders. If the software come to an end, usually the developer without interest and motivation. Then there may be another person to take over, and then raised the idea of user groups, be extended and improved. General development of a “release early, release often” principle, for example, fetch the development will have two to three hundred of volunteers as a test population. Market advantage is a multi-testers, and high quality, can feed a number of high-quality bug reports, or even to amend the program or patch.
But in fact, the content of the book may not have passed the “generalities”, we know. Reading this book, I also hope that more information on the comparison between the Cathedral and the Bazaar, but there is not much, and only know the benefits of market, very few mentioned the benefits of the cathedral and the bazaar disadvantages. With extreme suspicion, the article not pertinent.
In fact, I also hope that analysis of the market there is the possibility of what the profit drivers, and the Cathedral of the benefits and drawbacks.
Sorry, the comment form is closed at this time.