In the past, when I first entered the industry, I always made these common mistakes, which later turned out to be true SBs. Of course every programmer will make mistakes, the important thing is to learn from them and grow. So what exactly are these errors? I'll take a look at it for you! ! !
When I feel like the code I'm testing is a bit awesome, the reality is...
The interface I designed and the interface called by others
Even the test of wearing NIKE shoes is nervous on the side, but a little happy on the inside
We always have to embrace change, but unfortunately I understand it too late.” Lying on the hospital bed, I regretted it too much.
It's obviously a small bug, but it can't be fixed.
4 directions to the ultimate bug
In many years of testing experience, it is often found that there is such a phenomenon: there are always some bugs mentioned that cannot be fixed smoothly. These bugs tend to have 4 directions:
-
1. It was finally resolved in the found version, but it took a lot of trouble in the middle.
-
2. It is planned to be resolved in subsequent versions.
-
3. Decided to never fix it, but turned into a potential bomb and was forced to fix it in subsequent versions.
-
4. Decided to never fix it, and it hasn't been fixed so far.
I stumbled across the code I wrote many years ago
Who am I and where am I?
There is only one word in my heart, mother save me
Java VS C++
function first and then
I want to learn HTML programming language 
Git code merging 
software development project
On the left is the effect that the customer needs, and on the right is the actual delivery result
When customer needs and results are often different, we always regret it
. Programming as a team 
Debugging CSS 
Senior developers Refactoring code
I still want to advise novice programmers a few points
-
Understand the requirements and start writing code
-
Be sure to remember to communicate more with the other party when you get the demand
-
The code must be well commented in time and in detail
-
Don't complain if you need to change, you have to learn to accept it. Life is not about poetry and distance.
-
If your technology does not serve the company's business, it will be worthless, you have to contribute your own value
-
Don't underestimate the importance of code quality, check, verify, and modify more, and then give it to others when you have finished the test yourself and there is no problem
-
When you encounter a problem that you do not understand, you must first try to solve it yourself
Finally, I wish everyone an early success in learning and a satisfactory offer