Although the sparrow is small, it is very complicated: What makes the simple problem complicated?

"The Sparrow is small and dirty
"Series
---
This series focuses on 1.1 drops in daily work and starts from the details to discover the joy and wisdom of work.

---

This article is not about technical issues, but about communication and working methods.

Our company has a software product, which is still in a stable stage with a low degree of productization,

This product is currently being implemented in a national project.

The implementation team was sent to the provinces for on-site installation and debugging,

Because product development and user customization requirements cannot be completely separated, patch packages are continuously released,
Each time the implementers obtain the patch, they will perform the upgrade on site.

A is the project manager responsible for implementation in several provinces, and B is the person in charge of a product module development team,

In February April, major functional adjustments were made to the module in charge of B. After patches were released, a was on-site upgrading and found exceptions.
As a result, developers from afaction went to the site to inspect and found that there were missing files,

The problem was fixed by developers on the site, and everyone did not go into any further reasons.

Due to the large adjustment of B's functions, the patch packages were released several times in succession for more than a month,

Every time there is a problem after update, developers need to be dispatched to the site to solve the problem.

After repeated attempts, as the pressure on preliminary acceptance increases, A and B have been on the phone for many times,

A finally couldn't help it. He thought there was a problem with the patches released by the R & D department,
Send an email to the department leader to resolve the issue.

After I took over the investigation, I asked a to package the problematic system that had just been upgraded at the site to me,
First, I need to reproduce the problems he encountered at the site at the company to eliminate environmental factors.

(Because every time there is a problem with him, I first doubt whether there is a problem with his environment ).

I got the package from a and tested the problem he mentioned. I further checked the cause and found that there was still a lack of files,
I asked B for the latest patch and confirmed his upgrade steps with.

The information is summarized in one place, and the truth is actually very simple, or even silly:
B. the incremental update package released each time only contains the files that have changed compared with the previous release,

Each time a is upgraded, it is replaced by directory instead of overwriting.
As a result, files that have not been changed in the directory are deleted.

---

Comments:

This is an easy-to-find error,
When developers first go to the site to help implementers update,
If both parties make effective communication, the problem should be solved.

It can be seen that communication is a wonderful thing, and it has nothing to do with distance and language,
If both parties can try to understand each other, rather than trying to draw a boundary of responsibility,

There may be many problems.

After reading this article, some people may think how such a low-level error occurs at work,

I also have this question, but it does happen, so record it.