The New Year is coming, I have to feel the time. Unconscious, I also played my life. It is said that this year is sad, but I don't know who I have a good faith. In any case, I wish you all the best of this blog of friends, tongren, brothers and sisters.
In the end of the year, in addition to being busy delivery, outside the case, I have to hit the ninety-nine nine is what this year's performance is. Usually, the company will develop a good-year KPI at the end of the year. Let's not to mention the international brand of our company 20, which is very rigorous in this regard. This is a very rigorous, how to make a remember, at least it is still reserved.
In the meantime, I remember that there is a bug of kloc in this year's KPI. Translated into Chinese is a thousand lines of bugs. One year, I am not busy, and the code has written a pile of one. Turning over the ClearQuest, not exclaimed, BUG is so much. I still remember that I didn't believe this is my own BUG when I saw it. I am still very confident about my code level, I have written C and C . Send it to the military. How to use C # in this year, so much. After calm down, carefully analyze these bugs.
This analysis is summarized, and it is very rigorous because the pure personal mistakes are very small. After all, the people who write C will be very rigorous. The most due to the changes caused by the demand change, the next is because the N more errors caused by other people's interface changes. There is also some interfaces (most hate is this). Perhaps, these can give me a lot of reasons to explain that they are not as bad, but the end of the year, I want to be 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 see what it will respond.
I still remember that a joke in Winberge, God asked the programmer's greater achievement this year, the programmer said that BUG was half. God can't understand what bug is, ask the prime minister. The prime minister is awkward, the God is gone, and there is no BUG, and every year, the programmer will say that there is 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". I think more about talking about our different roles to see the appropriate reaction, a suitable reaction, a saying.
First of all, it is of course a person who writes the code. Usually the programmer or software engineer. I have worked hard a year to see my own bug, and it is a bit shameful and shameful. I can't pull down 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, and the individual has improved space, and this improves yourself. The first thing to do is to categorize these BUG. Classify from demand, analysis, design, code, borders, deployment, etc. I have found that most bugs are actually a code error in design errors rather than a simple meaning. I believe that a language will rarely lead to errors because of pure syntax, and each problem has countless solutions, and it is not easy to divide. Therefore, the problem is usually in the face of the needs, we have made mistakes when we face the problem. These error decisions may come from all assumptions that do not understand the actual situation, the boundary module that has changed, or the problem of processing methods. Part is an attitude, there is also a part of the level is not scientific. In fact, this matter is the way to find itself, we can improve your own way of analyze the problem, thus upgrading yourself to solve the problem. Ability, expand personal solutions and ways. And the attitude is mainly communicating. The feeling of programmers gives people a relatively occasionally occluded, not willing to deal with people. Indeed, it should be communicated as part of vocational skills as a software engineer having a professional literacy. We should build a platform with people exchanged on the ability and the machine communication. Second, it is the project manager. I personally think that his attitude towards BUG is extremely important in the organization. After all, it is a person who is underway. 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 bugs are also indirectly affected by their behavioral changes to the daily work of the following people. So, I think the project manager faces BUG should show the greatest cooling and the most tolerant mentality. When you see BUG data, it is simpler than the biggest contribution to Bug. After all, the difficulty of different modules in the project is different, even if it is the same thing, what is different from people will lead to different results. The most typical is the quality of demand. The impact on bugs should be said to be the largest. Therefore, I think the project manager should first analyze which class of bugs have the greatest impact on the project. If the defect management tool is good, this should be easy. Usually, it should be directly reflected in the brain whether it should be a progress that is too big to cause a little pressure. Is it a good quality of the workpiece, whether there is no good communication platform, do you have something too martial arts? There is no opinion that everyone hears, causing baseline deviations. If it is really these questions, I think it should be not too difficult to improve, and AC can promote milling. For example, the phenomenon of catching work is serious, you can explain the market with everyone] The pressure is too strong, and the competitors are too strong. Enter the workpiece, you can find the parties or their supervisors, and strive for their legitimate interests. It is good to say if the week will be opened, and whether the weekly report is seen. Conversely, if it is found that BUG is not communicated in time, it is naturally large. After all, this is also part of the performance. Moreover, the programmer usually feels that he is very wronged. If many things don't communicate, they will think that the other party will only take care of others, but they are all working on the boss, belonging to the class brother, the people's internal contradiction.
