News Articles Download Algorithm Code area

How programmers guarantee no BUG!

There is no doubt that the programmer is good at thinking of the owners. A procedure for the preparation through: Reflections on the design, development, debugging, testing and operation of these basic stage. However, most programmers have a problem is not willing to test their code. They hastily after the completion of the transfer of work on that end, the test is to test the work.

According to theory, if the code problems, the Test and eventually the user can certainly find these BUG, which time and wait for the return to the issue in the end to find what is wrong in no small cost, its costs are:

1. Affected the reputation of their own programmers

2. Impact on the quality of the product

3. Impact on the customer's trust

4. DEBUG again this time of difficulty has increased many.

Not big, say more than it affected the reputation of their own. If you always have such procedures as the BUG, you get income would be reduced, even if you write a lot of code.

In fact, the last point is also very important in the face of a code of our time, what methods can be easily handled, but if this code will prevent the huge system, a simple question can not be immediately identified. In order to consider their own, saving themselves DEBUG the time, we should give our procedures as far as possible not BUG.

So how can we guarantee their own kind of code to not BUG

Programmers must overcome some of the fatal shortcomings of their own in order to fundamentally solve this problem. Well, this is what «we have mentioned earlier, the programmers of their code are very tolerant and think that is correct there is no problem. In fact this kind of thinking more normal, the process is designed by programmers thinking and only after written, programmers will not own the right things that do not write code, and this time have been to assume that the process is correct, but Non-saints, how can it not to make mistakes. In fact programmers in the treatment of other programmers on the attitude of a good time, and learning with a critical attitude, but once treated their own code it will be difficult to do so, it is the most deadly. Programmers must also find fault with their own code and learn the attitude of this is based on the assumption that their code is wrong, and then need to do is prove that they like how the code is correct. Programmers in the process itself can be generated at each stage of work to do: careful design (this time painting is worth the time, we must ensure that their procedures have a clear outline of hands before starting to write), prepared by the code, Unit testing (unit testing in the importance of not Zhuixu), and functional testing.

The design carefully: this is said in the carefully programmers to write code before the code must be the entire structure of a clear and logical structure of a clear understanding, only this time we can to write code. There is no on the document, but I said that the idea must be clear, but clear thinking is not everyone can head directly in the form, many people are ordinary people, not the head of the Kuala want to all the problems Clearly, then note, especially for complex logic.

The preparation of the code: the code for not sure, for example: the new design of algorithms, the best guarantee for its accuracy. Can separate part of this test, which allows modular code at the same time guarantee the correctness of the code. Sentence: a small amount of code and ensure quality is still relatively simple.

Unit testing: unit testing of the importance of Syria not to repeat now, there are many tools to help programmers and reduce the workload.

Functional test: programmers guarantee the quality of their code the final hurdle; In order to do this kind of work we may have to write some code to test, or even testing. CASE to use a lot of testing, and the wrong CASE. Here and testing the test difference is: let programmers are still the focus on its own within the framework of the code, reduce the debugging more difficult.

If you through the above steps are not find you in the process have any questions, then I think the procedure should be a strong enough. In fact, there is another point to note is: code REVIEW.

In front of the programmers treat others said the code's attitude is critical and learning attitude, so let other programmers to REVIEW your code inspection procedures also have very good logic wrong way. Team should be cross-REVIEW code, which is practical experience.

As a programmer must have more good habits, and treat their children as the code, we must cherish our code, the code also let go the right direction.

View：(107) comments：(0)


Nickname:
comments: