Senior Test / development programmers write no bugs? Qualifications (shackles) don't be afraid of mistakes

---

Preface

Senior Test / Development programmers write down none bug

On the network , There are many definitions of excellent programmers . In the daily production process , Especially leaders , I will feel that as an excellent senior programmer , Should write no , Or rarely and slightly bug, But this is not mentioned in the description of excellent program apes on the Internet .

in fact , I don't know whether these senior programmers have not reached the master level , Or as a person , Is not able to make a flawless code perfectly . When the code written by senior programmers is found bug, Different roles , What's your opinion ？

Although the senior programmer is a light bad , At the same time, it is also an extremely heavy constraint . As long as I am a programmer , There is a chance to write bug Code for . At this time , Your boss , colleagues , subordinate , Even myself , Will doubt their own level .

You can't be wrong if you don't , therefore , The most comfortable way is not to write code , After fame and fortune, he retreated , Keep the fruits of victory and immortality , From now on, only spray other people's code , Anyway, more than one person sprayed , If something goes wrong, you won't die .

that , At first, people who had a pure pursuit of writing code , With seniority （ chains ） The deepening of , Where to go ？

Maybe there is no bug Think about it , Although there are tdd, Double review and other means to avoid bug The introduction of , however , As long as it's people , There are weaknesses , Blind spots , Luck and accommodation , This seems to be the excuse and cover cloth of coder , But no one knows coder better than coder , That's what it is . To paraphrase , Only one thing can be proved wrong , And cannot prove a thing is right .

Writing code is very tiring , Many times it's repetitive work , But if you don't write code , Always look at the flowers through a layer of fog . Maybe you can describe the picture beautifully , And no one asks whether you are like this , There is no need to be responsible for problems , however 10 After year , Maybe a successful career “ Mediocre ” Will be born again , And he is definitely not a master .

My advice is , Non repetitive code , You still have to do it yourself , Don't be afraid of mistakes , Calm down and , Write sentence by sentence , Harvest will come .

Here's what I did 2022 The most complete software testing engineer in the year learned the knowledge architecture diagram

One 、Python Introduction to programming to mastery

Two 、 Interface automation project practice

3、 ... and 、Web Automation project practice

Four 、App Automation project practice

5、 ... and 、 Resume of the first-line big factory

6、 ... and 、 Test Development DevOps system

7、 ... and 、 Common automated testing tools

8、 ... and 、JMeter Performance testing

Nine 、 summary

Only don't forget the original intention , To have a beginning and an end . When you want to give up , Just think about how you did your best at the beginning ; When you want to escape , Just look back at the original firm and persistent you .

No one will care how much effort you have made , Do you feel tired , It doesn't hurt to fall , They will only see where you stand last , Then envy or despise . For the beauty of the future , It must be a little bitter now .

---