Programmers change bugs

Programmers change bugs

Programmers modify bugs. Many new students who have just graduated from the company have to go through the learning process for a period of time, so that the company's leaders can truly invest in project development. This learning process may be reading the source code, or modifying the bug. I think most of them have experienced such a thing.

In fact, programmers are also learned to change bugs. Programmers change bugs in the same way as doctors do. One is to treat machines, and the other is to treat people. First, you must accurately locate the cause of the bug. To locate the problem, the programmer needs to read the code, understand the process, and understand the ins and outs. Second, after locating the bug source, you need to analyze the solution to the problem. To analyze the problem, you need to combine relevant knowledge, familiarize yourself with some of the mechanisms used by the problem, and find the best solution. For Android, for example, to modify the WiFi bug, you need to figure out the Wi-Fi process, statemachine mechanism, and message mechanism. Of course, the four most basic components and mechanisms are essential, it is useful everywhere. Then, it is coding. Of course, coding should also pay attention to some issues. For example, the style should be consistent with the source code as much as possible. Google's programmers are still competent. Note must be clear, including the author, change time, and reason. Finally, we should emphasize that bug modification must be thorough. You cannot change one bug to another or a bunch of bugs. This situation must be avoided. Our company is a programmer who just graduated from college. The bug change is not complete, but the interface display is changed, and the actual functions are discarded. For such code, I just want to say two words: Spam. In addition, the bug change should be discussed with engineers of relevant modules, because they may be experts in this field so that they can write excellent code.

Some people change the bug for several months, and they will split the development tasks or tasks with a higher level. Some people keep changing bugs as soon as they enter the company. It is undeniable that the company has some problems. But programmers should also look for problems from their own aspects. Is the code you write the most efficient? Does the code you write make it easy for others to understand? The bug you wrote makes others stunned? If you do not do well enough, do not complain all day: "Let me change the bug again. I have been changing the bug since I started the company !"