"Is there a simpler way?" Ma Yun asked.

"Yes!" the supervisor nodded. "In fact, there is no problem with our program, but there is a problem with this new patch. So we just need to delete this patch from the system, then everything will be fine and all problems can be solved!"

"Delete this patch?" Ma Yun was stunned. "Will this pose a risk to the whole system?"

"No, this patch is actually an independent detection software. Although it is integrated into the system file, it is essentially independent. Deleting it will not have any impact on the system, let alone destroy the stability!" the main technology pipeline.

"How long will it take?" Ma Yun asked again.

"Two hours!" the supervisor put up two fingers and said, "in short, we just need to issue an announcement to guide users to find the corresponding folders and patches, and then delete them!"

"If it's more complicated, we can make a fool's bag for customers to download, then double-click, and then click several confirmation pop-up windows that pop up automatically. This fool's bag can automatically delete the corresponding patch."

"The writing speed of this fool's package is very fast. Two hours is enough!"

"Good, that's it!" Ma Yun said with a smile. "You go and arrange for them to finish the fool bag quickly, and then publish it to our official forum and the official download channel, so that everyone can download it!"

"Also, you draft an announcement, and then publish it to all users through our QQ system account. Tell them to go to this download address to download the fool package and solve the problem of crash!"

"Yes!"

"Well, everyone has been working hard for a day. After the fool's bag is written, everyone will have a rest from work!" Ma Yun was lazy, and everyone was relieved, and then went to solve the problem respectively.

In Ma Yun's view at this time, this is just a very ordinary accident. Although the impact of this accident is not small, many people in the technology department have dark circles.

But this is really just a small problem. After all, a fool's bag can solve things. Ma Yun can't imagine that this will be the first hard battle in his life and a hard battle that can be recorded in the history of the network.

It is called soft Q war in history.

——————————

"I don't know what kind of expression these stupid Chinese people will have when they see our gifts!" almost at the same time, several engineers working in Microsoft's technology department talked with smiles.

"No, they don't know there's a problem yet. Their customer service is still sleeping!" another person said with a smile.

"Even if they find a problem, they will never expect that the bug will be hidden in our patch."

"Besides, it will take us at least a week to find the problem! How can they have our speed!" another engineer said.

"Yes, let's make a bet. I'll bet $100. These Chinese people don't have half a month to find out what the problem is!" the original engineer laughed.

"No, I bet with you, but I bet they won't find us until a month later!" another engineer immediately replied.

"Ha ha!" all the engineers burst into laughter.

There is nothing wrong with the ideas of these engineers, because it is very difficult to find problems in the United States and Microsoft, even in a week.

First of all, after the problem occurs, it will not be reflected in the Engineer at the first time, but will complain to the customer service department.

After receiving the complaint, Microsoft's customer service department first appeases their customers for good words. Only after the customers hang up, they will not directly reflect the problem to the technology department, but record it in their own work records.

Well, if the customer service happens to be in a bad mood, it's normal not to record.

At the same time, according to Microsoft's practice, the work records of customer service will be submitted to the leader of the customer service department after the end of the day, and then the leader will check the problems, select some serious problems and give them to the superior leader.

The leaders at the next higher level will collect these problems and submit them to the head of the technical department at the meeting twice a week.

For this step alone, if you are lucky, you need to wait for three days. If you are unlucky, you will directly hand it over to the technical department in a week.

Assuming that the problem appears in front of the technology department within three days, the leader of the technology department must first send someone to count and select the problem, which will take another day or so.

After selecting some problems to be solved, the person in charge needs to report to the above, get the approval from the above, and the problems will be transferred to the relevant engineers of the technical department to solve the problems.

However, because many engineers will accumulate a large number of tasks, once these problems fall into the hands of engineers, I'm afraid they will have to accumulate for several days before engineers can really start to look at this problem and think about solutions to the problem.

If it is a small problem that the engineer can solve by himself, he will report it to his leader and add it to the patch after approval.

If the engineer can't solve the problem by himself, then he needs to wait for another day or two, wait until the regular meeting of the technical department, and take out the problem at the meeting for everyone to discuss, judge the seriousness of the problem, whether it needs to be solved immediately, and how much effort needs to be invested to solve it.

Anyway, if such a process comes down, half a month will definitely be gone. When the problem is really solved, a month is too fast.

Before 2008, before the strong rise of Huaxia in the network field, all network companies, or all companies, were basically pissed. If you reflect that a problem can be solved in a month, even if it is a conscientious enterprise, it is normal to delay for a year, or even throw the problem directly into the dustbin.

After all, compared with solving problems, ignoring problems is the fastest, easiest, simplest and most cost-effective solution.

Don't think this is too exaggerated. On the contrary, this is a very normal thing and a problem that any large enterprise will have. It is collectively referred to as large enterprise disease. This is an unavoidable time.

So these Microsoft engineers are very confident to bet that they can solve the problem within a month. They have looked up to too many Chinese people.

"Let's gamble again. After they find out the problem, how to solve our gifts!" an engineer thought that one gamble was not enough. He had to gamble for the second time.

"Then it's longer. It's impossible without less than half a year!" an engineer immediately replied.

"No, I think it will be more than half a year. After all, we are designed for their bottom results. If they want to solve the problem, they have to replace more than half of the programs. It also involves different versions in more than 20 languages. It is impossible without half a year!"

"Yes, half a year later, they solved the problem and replaced it with a new network protocol. At that time, we only need to write a new patch, and we can continue to send QQ to God! Ha ha!"

Hearing this, all the engineers laughed happily.