Today at about 1-2 o'clock at noon, I happened to take a nap to recharge my batteries. Otherwise, how would I write and correct bugs in the afternoon? Suddenly, the WeChat voice and mobile phone rang at the same time. It turned out that they were both customers of the same company, just two different people.

At this time, my heart began to race, "Damn it, can you have some love? It's noon."

The other party said that some data from the mini program could not be returned, and they wanted to help find out what the problem was. In fact, all developers know that what they are most afraid of hearing is "there is a problem with some data", "this problem occurred after passing xx, passing yy, and passing zz", "a certain problem suddenly appeared today, but it no longer occurs".

Because this kind of problem usually means that the bug is hidden deep and a lot of brain cells need to be killed.

Then I immediately went to check one of the API interfaces, and found that the network was not connected... Then I tried to access other API interfaces, but the network was not connected...; and then I accessed other interfaces that the user had not reported, but the network was still not connected. As a result, direct access to the server still failed.

Yes, that's right, the server is down.

Of course, even if it hangs, we still have to help users solve the problem. Although our code has long been accepted by the other party's technical team and handed over to them for maintenance, isn't it true that "the customer is God"? Still communicated with the user to help him solve the problem. Because the number of visits to this project is not large, and it can be basically concluded that the software does not have fatal bugs (enough to cause the server to crash); later users said that they would communicate with me internally first and then contact me.