The project management personnel who have done Leader in Japanese enterprises prefer REVIEW. This morning, I received Email, mentioned: "Quality is made, not detected; high quality is not equal to high cost, high quality is the prevention *" ... "test is verified, not guaranteed Quality. High quality does not have to add more people, extend the delivery period. Improve quality, have a good design, strict implementation (process management / configuration management, including review) ". Combining usual experience, the so-called process management and configuration management is more virtual, but it is REVIEW, once it is mentioned, it is a solution to the BUG. Plus * The sentence is originally a business rumor from a traditional fast food company, which is turned over by the length of the class. However, traditional companies and software development have a lot of different, so simpler ratio (seems to have more people like to compare software development and traditional enterprises, and take a better name, called "software engineering"), I don't agree . Here are some simple analysis of the core development of the software in people, in one of the individual programmers, no matter what process control, people are uncontrollable (there is time I want to write process control and people's control) BLOG, that is, you must respect each developer, rather than seeing them from the perspective of production machine, fundamentally explaining the difference between traditional enterprises and software development. So you should look at the test in different eyes, and all the production processes. Second, in traditional enterprises, the test is for testing, but as a development personnel, I think in software development, the test in addition to testing code and logic, more is a developer's thinking process (this It is especially important in the UT process). Every test iteration is likely to generate new needs and better solutions, but can REVIEW can have such effects? Third, each module developed by software has its own characteristics (this is the development of the current phase), and the logic and methods of different developers are different, and the REVIEW people are difficult to go thoroughly in a short time. Understanding developers' views and methods, it is difficult to find true, deep BUG, up to the graphics logic, discover some problems. In summary, I think REVIEW does not reduce Bug's panacea, and as XP is produced, the role of Review can be less and less, and the future development will evolve what is like, we Waiting for it.
