How often have you been working on a development project that ran into an online bug and thought, “This isn’t my pot, let it go.” After writing the code, faint feeling there is a problem, but the program runs well, use it first; Take over an old system, this what broken code, forget it, change it change will use……
Potholes bypassed today will double back tomorrow:
The next time you change this code, you’ll still run into it, and you’ll have to go through it line by line; Some scene online triggers the problem code, causing an unexpected crash; The old system is too time-consuming to change and easy to step on the pit, it is better to spend time to rebuild.
The test teased you about the bug you wrote, and you denied it, saying it was a hole dug by others. PM change requirements said here only added a small function, when you just want to dig a hole, crash into a sinkhole. Have you noticed that every day’s work is actually filling in one hole after another?
Pit filling power is one of the core skills programmers should have.
Potholing capacity is ultimately the ability to solve problems
When was the last time you grew up fast? CtrlC,CtrlV? Or do you talk about the business framework you know?
You don’t grow in prosperity, you grow in adversity: moving to a new company to learn a whole new business and technology framework, improving as you make mistakes; The company wants to introduce some new technology, and you’re assigned a month to complete the migration, so you’re busy digging through technical documents after work and writing demos at home on weekends…
When I got up from the pit, I realized that my previous problems were actually opportunities for growth.
In the “3Q war” that shocked the Internet a few years ago, 360 dug a sinkhole for Tencent, and Tencent struggled to fill the pit. Then Ma huateng wrote in a letter to his staff, “If 360 had not been in trouble, we would not have had so much reflection and comprehension.” Maybe one day, when we reach new heights, we will be grateful for the training of today’s opponents.
Subsequently Tencent changed the direction of strategic development, towards “open”.
We seem to live in a pit all the time: digging holes, falling holes, filling holes. If you don’t like it, only when you try to fill up the pit under you, and then move on to the next pit, and so on, can you have real growth.
Although programmers often advocate “you carry my burden, you fill my hole”. But please don’t dig the lower pits:
1. Sinkholes: No notes
Schedule tension, the new sea yu in a hurry to pile up the code will apply for test. But his TL one sentence will give him to hit back to rewrite: a line of notes do not write who can understand!
According to one developer, comments are just as important as code. Comments need to be written so clearly that testers and even PM can read your code to be a qualified programmer.
2. Mountain pit: do not write interface documents
Some companies before and after the end of the joint adjustment basic roar, “the elder brothers, a parameter less transmission”, “this field is capitalized”, “you pass so much I useless, forget it, put it”……
I have seen an email testing reject development: The front-end did not pass a parameter, which caused the process to fail, Reject.
Technical personnel usually do not like to write documents or do not want to spend time on documents, resulting in the development of the front and back end of their own, there is no standard, if you need to connect with the external system, you have to go through the code to find interface parameters. Interface document can save the time of communication and reduce the introduction of bugs and improve the quality of code.
3. Pit: Expansion features are not considered
Code that doesn’t decouple and doesn’t take into account future design expansions is creating holes for teammates.
In addition to the top holes, there are instructions for digging holes below:
There is no real-time fault tolerance, the program only according to their own brain “taken for granted” trajectory;
Placing judgment in layers of bottomless logic;
One method writes thousands of lines and no one dares to touch it.
Never test yourself.
“I am an old programmer who has been working on the front-end for 5 years. I resigned and now work as a lecturer. At the beginning of this year, I spent a month organizing a list of web front-end products that are most suitable for learning in 2019, including the most basic HTML+CSS+JS, mobile HTML5 and various frameworks. Welcome beginners and advanced friends.”
Add QQ group: 645199623 (recruiting)
Add micro: QD_666_QD