Share the honor and disgrace of the programmer team spirit

As a member of a team, we need to put the honor and disgrace of the entire team first. This seems to be a manifestation of the spirit of collectivism, which is incompatible with the more popular personal-centered Thinking. However, only by putting the interests of the entire team at the top can the team develop and progress. The development and progress of the Team will certainly benefit every member.

 

Here I would like to talk about a very typical situation. There are usually developers and quality management personnel in the team (that is, our testers ), generally, both roles are family members. The former is very afraid of numerous problems detected during the latter's testing, while the latter often complains that "You did not test it yourself ". It seems that there is always an irreconcilable conflict between the two.

To solve this problem, we need to clarify the principle of Honor and Disgrace. The purpose of developers is to develop highly efficient and high-quality products.ProgramFirst of all, we need to raise requirements for ourselves. If the quality of the developed program is not high, it will inevitably be modified and reworked. It seems that at that time, we saved our time, I submitted the program as soon as possible, but in fact, I still need to modify it later, saving the time and returning it. On the other hand, the tester also needs to point out low-level problems, (The problem can be avoided if you are a little more careful.) It also wastes the testing staff's time. As a result, it takes two times for the team. If you think of saving time for the team, you will consciously improve the quality of your program.

 

For the quality management personnel, Cai zinan should first carefully test the problem, which can save time and easily establish a good relationship with developers, but it will definitely lead to a decline in program quality. For customers, quality is the lifeline of the program. Secondly, we cannot be complacent because we discover many defects. Indeed, this means that as a quality manager, our work is well done, but what is our purpose? It is not to find more defects, but to improve the overall quality of the system. I think we can summarize and classify defects, and then submit our analysis results to the entire team, pointing out where mistakes are easy to make, which not only improves the development quality of the entire team, it also saves time for your future work, but it won't always find so many defects.