Shulou(Shulou.com)06/03 Report--

"5 minutes from student to programmer" lesson 12.

Last lesson we briefly mentioned that after writing the code, we should try out the function. If we are satisfied with the function, the user will be satisfied, and at the same time, we can reduce the bug rate and rework. In this class, I will share with you how to use tests to improve your ability and even your position.

1. What decided you in this position?

Determine where we are, not how many skills we can, what skills we master, but what is in our hearts! Those with functions in their hearts are junior engineers, those with modules in their hearts are intermediate engineers, those with applications are senior engineers, and those with enterprises in their hearts are bosses.

You say you are very good, proficient in java, springboot, springcloud, mysql, MyBatis; and even front-end HTML, css, JS. Do people believe it? You may or may not believe it. Why? No one else can tell.

The labor result of junior engineer is function, so function is the most important measure to test the ability of junior engineer. If the bug rate of function is higher than the average level, it means your ability is very low. If the bug rate of function is lower than the average level, it means your ability is good.

If the average bug rate of the function is 2, and you say your bug rate is 1, others will like you and think you are awesome.

two。 Look at cause and effect in the short story of the workplace

Story 1: I have set up several teams, and when the team has just finished the project, there are often tests to complain to me, saying that who has a lot of bug, who fails the smoke test, who leaves the test before the completion of the function, and so on. So I'm not the only one who cares about functional quality, but test engineers are more concerned, because poor code will increase their workload.

The technical manager said, "I want Zhang San and Li Si." The test manager will say: Zhang San is no good, he is not very serious, every time he has the most bug, we still do not want him, I think we still want Wang Wu, he is very rigorous in doing things, and it is very comfortable to cooperate with him.

You see, if you don't take things seriously, bug is the most, and people don't want you yet. If the company has done the final elimination, that three is the target to be eliminated. If the company happens to have a transfer quota, it must be one of the top five.

The previous stories are all about the workplace, so let's take a look at the help that tests can bring to our skills improvement.

3. The upgrading of technology

If you test more and try more, you will find that with a similar interface, why is the master's writing better than mine? Analysis of the interface, and even to see the master's code, found that the master uses a unified UI style, he is done according to the UI design, UI is marked to do well, UI is not marked, do it blindly. If you find the gap, you will know how to use UI specification later.

You may also find that I did the same interface switch in a flash, but the master's switch is very smooth. If you look at the code, or ask the master for advice, it turns out that he added animation effects when switching. Then you will know how to deal with the interactive effect.

4. The improvement of product understanding

Like the example of sending text in the last lesson, during the trial, you may find that when the app side is doing the design, it is written in 4 steps, but in the third step, I quit the chat interface, so what to do with this? During the trial, it is found that there is a missing step, and before the test is submitted, add the processing of this operation as soon as possible, and the completion of the function will be better.

In the previous analysis, I temporarily said that this function had nothing to do with other functions. During the trial, I found that in the chat interface, in addition to sending text, but also sending expressions, pictures, and so on, it had something to do with other functions. In an one-on-one chat, you can also call the address book and add a group chat with friends, all of which are relevant.

Then, I realized that the original product logic was designed like this. When the master received this module, how did he divide the module into various functions, and then give it to different people to do?

5. I am a developer, why should I understand the product?

You might say, I'm a developer, so why should I understand the product? We borrowed the small pocket of Dingdang Cat and put the time back for a year. Zhang Sancheng, as an intermediate engineer, also began to bring his apprentice. What a feeling of excitement. Now taking part in a new project, the technical manager pulls middle and senior engineers Zhang San, Li Si and Wang Wu together: "Zhang San, you are in charge of the user module; Li Si, you are in charge of the commodity module; Wang Wu, you are in charge of the payment module. Is there anything wrong with this arrangement?" Then Zhang San stood up and said, "Boss, what are the functions of the user module?"

It's funny when this happens. We can imagine how funny the scene was at that time. Intermediate engineers should have an understanding of the products and know how to decompose the modules into individual functions. How did this ability come from? Is there anyone to teach? This kind of ability is not taught, it is the accumulation of experience, and it comes from playing one function after another.

This side talks about the cause and effect behind R & D and testing, and here we also see the cause and effect behind R & D and products. Some people may feel uncomfortable after reading the word cause and effect. This is nothing. Cause and effect is the if statement. If the condition of if is met, the code segment of if will be executed. This is called cause and effect.

6. Low Bug rate will bring confidence, self-confidence will expand the scope of responsibility

If you do the function, the bug rate is less than others, are you more confident? That's for sure. When you have self-confidence, do you dare to take more responsibilities? As we said earlier, it is not the technical level that determines the level of the engineer, but which aspect of the responsibility he bears. Function assume more, slowly assume the responsibility of the module, as long as you can assume the responsibility of the module, that is the intermediate engineer level.

Just wait for a transfer and a raise.

7. Summary

In this lesson, we share the value that testing brings to programmers. Through trial and testing, programmers can improve their technical level, understand the products, and reduce the Bug rate of functions, while low Bug rates can increase programmers' confidence and have more confidence to assume more responsibilities, while more responsibilities reach the module level, and his level will be promoted to intermediate programmers.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.