"5 minutes from the student to the programmer" Lesson 12.
Last time we simply put down, after finished the code, try to function, the function of their own satisfaction, users will be satisfied, while reducing bug and rework. This lesson I share with you how to use the test to improve their abilities, and even improve their positions.
1. What is your decision in this post
We decide what position, will not have much technical, What skills, but what our hearts filled with! The primary function of mind, engineer, and my heart is filled with modules of mid-level engineers, application of mind, is a senior engineer, and my heart is filled with business owners.
You say he is very powerful, proficient in java, springboot, springcloud, mysql, MyBatis; even the front-end HTML, css, JS also proficient. Others believe it? You may believe or may not believe, and why? Others can not judge.
Junior engineer fruits of labor is a function, so the primary function is to test the ability to engineer the most important measure, if the function of the bug is higher than average, indicating your ability very time, if the bug rate function below average, indicating your very good.
If the average bug rate function is 2, you say your bug rate is 1, people will thumbs up, you feel terrible.
2. workplace stories to see cause and effect
1 story: I set up several teams, in a team setting up just doing the project, there is often tests complained to me that a particularly large number who bug, who pass the smoke test also provides measurements, who did not function done it threw testing, and so on. So my concern is not just the quality function, test engineers more concerned, because of the poor quality of the code, it will increase their workload.
2 little story: When I set the project team, generally the first decisions of the business leader of the project, and then from them to discuss what people involved in the project. Technical Manager, said: I want John Doe two of them. Test Manager would say: John Doe No, he does things very seriously, always bug him most, we do not want him, I think it is to be king five, he's doing very rigorous, very comfortable with him.
You see things are not serious, bug most people still do not want you. If the company has to do end of the elimination, goes third is the object to be eliminated. If the company just have a transfer Kong places, but also the non-quota king five perfectly. So, you see the development of a test with the surface, eight pole could not beat the thing, cause and effect logic behind them is so complicated.
前面讲的都是职场上的故事，下面我们来看测试对我们技能提升会带来的帮助。
3. 技术的提升
你多测试，多试用，你就会发现，类似的界面，为什么师傅写出来的就比我好看？分析界面，甚至去看师傅的代码，发现原来是师傅采用统一的UI风格，自己是按UI设计图来做，UI上有标注的就做的好，UI上没标注的，自己瞎做。发现差距了，后面就懂得用UI规范了。
你可能又发现，同样的界面切换，我自己做的一闪就过去了，而师傅的是很平滑的切换，再一看代码，或向师傅请教，原来是他在切换的时候加了动画效果，后面就懂得交互效果的处理。
4. 产品理解的提升
像上节课发送文字的例子，在试用的时候，你可能就发现，app端做设计的时候，写的是4步，但是在第三步，我退出了聊天界面，那这个要怎么处理？试用的时候就发现，少了一个步骤，在还没提交测试前，那赶快添加对这个操作的处理，功能的完成度就更好。
之前分析的时候，暂时说这个功能跟其它功能没有关系，试用时就发现，在聊天界面，除了要发送文字，还要发送表情、图片等，那就跟其它功能有关系。在一对一聊天中，还可以调用通讯录，添加好友群聊，这些都有关系。
然后，就感悟到原来产品逻辑是这样设计的，师傅接到这个模块，他是怎么样把这个模块分成各个功能，然后再分给我们不同人做的。
这样，你对产品、对模块就了解了，是不是比你做完一个功能，丢给测试，等他反馈bug，再改bug好多了？
5. 我是做开发的，为什么要理解产品？
你可能会说，我是做开发的，为什么要理解产品？我们借用叮当猫的小口袋，把时间往后拉一年，张三成为了中级工程师，也开始带徒弟了，好兴奋的感觉。现在参与一个新项目，技术经理把中、高级工程师张三、李四、王五拉一起：“张三，你负责用户模块；李四，你负责商品模块；王五，你负责支付模块。这样安排有没有问题？” 然后张三站起来说：“老大，用户模块有哪些功能啊？”
This happens on the fun, we can imagine how the scene was funny. Mid-level engineers is to have understanding of the product, know how to break down modules into one function. The ability how come? Some people teach it? This ability is no one to teach, is the accumulation of experience, both from a functional play out of practice.
This face talk behind causal research and development with the test, which also saw the causality behind the development of products with the bar! Some may have looked at the causal word uncomfortable, this is no cause and effect is the if statement, if the conditions are met, if the execution of the code segment, this is called cause and effect.
6. Bug will bring low self-confidence, self-confidence will expand the scope of responsibility
If you do functionality, bug rate is less than the others, is not more confidence? This is for sure. You have self-confidence, they are not more willing to take on more responsibility. And we have said before, the decision is not technical level engineer level, but he assumed responsibility for which aspects. Function to take on more slowly assumed the responsibility from the module, as long as you take responsibility for the module, and that is the intermediate level engineers.
Waiting for transfer Kong liter salary bar.
7. Summary
This lesson we share the value of the test for programmers to bring, through trial and testing, programmers can enhance the technological level of understanding of the product can reduce the rate of functional Bug, Bug and low rates can increase the confidence of the programmer , more confident to take on more responsibility, more responsibility and reach the module level, he ascend to the level of mid-level programmers.