As a programmer, have you ever felt speechless and collapsed?

PM: It's simple, just a little. The programmer's nightmare is to get a product information at the end of the work. I made a little change, did you see it? What is even more frightening is that after several days of all-night development, the product said: the leader has just changed his mind and must add the previous functions. ? The product is always light, and it is not difficult for programmers to watch it, or it is not difficult to refactor the code. 10 One night is enough. So it's enough not to shoot the programmer three times.

2. No bugs found

The most painful thing in the world is that there is a bug in front of you but it can't be reproduced. Four or five years ago, the normal running application suddenly stopped running, and the log was checked around 2 pm, and there was no error, and it crashed. All simulation methods in the test environment may not be repeatable. This phenomenon lasted for more than a month, and when I was desperate, I found traces of spiders. At 2 pm Beijing time and 8 am Italy time, at that time, Italian users could log in to the system, and users with some special attributes did an operation. After one year, the code branch that ordinary users can't walk will directly trigger the system. This error was fixed in one line of code, but it is still reappearing for more than a month.

3. Take over bad code

For code editing, every programmer has his own unique coding style. So almost every programmer looks at other people's code with a bad eye. Once a programmer changes jobs, other programmers will definitely take over his projects, but if you look at the code, especially those who don't take notes, you will know that this programmer has actually scratched all his hair.

4. write a document?

I finally finished writing the code, just breathed a sigh of relief and wanted to start the next job. The leader said that the file was also added, and the meaning of interface parameters was written. The programmer's heart has always been unhappy and contradictory. As a result, the file was scribbled. This is because the code that realizes the function is a work that reflects its own value and makes money, and the file seems to be attached. Who wants to work more after work? Furthermore, is the time spent writing documents included in the workload estimation? Obviously, you didn't give me time, so let me write now. Let me work overtime. ?