When we face BUG
Author: Fuhong Xue (sammerkong@hotmail.com)
In addition to being busy delivery, in addition to the end of the year, the programmer is to consider this year's performance.
Usually, the company will develop a good year's KPI (Key Process Indication, Corporate Key Performance Indicators) at the end of each year, and our company has run 20 years of international brands, which is strict in this area. In the meantime, it is a thousand BUG rate that is Bugs / Kloc (Kline of Code) in KPI this year.
One year, the code wrote a lot, turning over the ClearQuest, not exclaimed, BUG is so much!
I still remember that I couldn't believe this is my own bug when I see it. Too much. I am still very confident about my code level, I used to write a program with C and C .
After calm down, carefully analyze these bugs. This analysis is summarized, and it is found that the BUG caused by pure personal mistakes is very rigorous because people who write C code are very rigorous. The reason for the occurrence of BUG is mainly because of the changes in demand; the next is because other people's interface changes; and there are some interface issues. Perhaps these can give me a lot of reasons to explain that they are not as bad. However, the end of the year, I want to be a professional defense, there is a KPI indicator requirement, what should I do? Do you have this opportunity to explain it? So I can't help but think that the supervisor will respond when it is bug.
I still remember that a joke in Winberge: God asked the programmer's greatest achievement this year. The programmer said that BUG is half. God can't understand what bug is, and then ask the prime minister. The prime minister whispering, God is anger, he is not allowed to have a bug. Since then, we will worship God every year, and the programmers say no bug this year. God is very happy, otherwise, only heard: God is very angry, the consequences are very serious.
It's a joke, Winberg also returned this as "Dictionary Magic". But I want to talk about our different characters to see the right reaction, a suitable reaction, a family!
Programmer
Usually, the programmer or software engineer, a year of hard work, seeing their own BUG, normal point is a bit shameful, and it can't pull this face.
I think this time is the most taboo thing to try to shirk responsibility or at all. In any case, there is bug that it means that there is still a defect, it is not perfect. If you have improved space, you will improve your own good things.
Based on the BUG classification of several aspects of demand, analysis, design, code, border, deployment, I found that most bugs are actually design errors rather than the code errors in the simple meaning. I believe a programmer's programming language rarely leads to errors because of pure syntax.
There are countless solutions to each problem, it is difficult to divide and bad. So usually the problem appears in the face of demand, we have made mistakes when we face a problem. These error decisions may come from all assumptions that are not found, do not understand the actual situation, have changed boundary modules or unscientific processing methods. There is also part of the attitude issues, and the method of doing things is not scientific.
We can improve our own way of analyze the problem, thereby enhancing our ability to solve the problem, expand the ideas and ways of individual solutions.
The attitude is mainly communicating. The feeling of programmers gives people a relatively occasionally occluded, not willing to deal with people. As a software engineer with higher professional literacy, communication should be communicated as part of vocational skills. We should also build a platform for one layer and people exchanged platforms with the ability to communicate with the machine.
2. Project Manager
I personally think that the project manager is extremely important to the BUG's attitude.
There are few opportunities below the people and high-level communication below the company, and the opinions are transmitted upwards through the project manager. The reactions of the high-level to BUG are also indirectly affected by the behavioral changes of the project manager to the following daily work. I think the project manager faces BUG should show the greatest cool and the most tolerant mentality. When you see BUG data, you will learn from Bug's responsibility. Who is it. After all, the difficulty of different modules in the project is different, even if it is the same thing, and the different people can lead to different results.
In the encounter bug, the project manager should consider: whether it is high due to progress issues, causing everyone to have too much pressure; whether the quality of the workpiece is too poor; whether there is a good communication platform; if you do things too martial arts, you didn't listen to everyone's opinion Result in baseline deviation, etc.
Because of these problems, BUG, the project manager should not be too difficult. Moreover, communication can facilitate the process of running between project members. For example, the phenomenon of catching work is serious, and you can explain that the market pressure is too large, the competitors are too strong; if you enter the workpiece, you can find the parties or their supervisors, and strive for their legitimate interests; every week insisted on the week; Everyone's weekly reporting project manager reviews and makes recommendations and comments.
Conversely, if you find that BUG is not communicating in time, the deactivation between project managers and project members will naturally become large. After all, this is also part of the performance. Many things are not in time and sincere communication, the programmer will think that they are very wronged, think that the project manager only doesn't consider others.
It is discovered in the program that bugs are inevitable. Only everyone work together, strive to improve the quality of the product, and the program can be faster and better, becoming a win-win situation.
------------------------------------------- I - Yes - None - Enemy - 分 - 隔 - 线 ----------------------------------------------------------------------------------------------------------------------------- ----------------
About the Author:
Name: Sammer
Nette: Sammer
Personal Education and Growth Experience: SEU is good at technical field: oo, uml, rup, pm current work Dynamics: Coding Person: Personal BLOG.9CBS.NET/QIUSHIKONGMSN: Sammerkong@hotmail.com
