This article is only a very small example, but in fact the ideas involved for your reference.

There is a requirement that is not developed by myself, and the person who develops and maintains this project has resigned. After the release, the front page was changed but not updated. Later, I was joined to check the problem, and found that they were full of some guesses, feeling that there is no specific troubleshooting scheme, and the reason has not been found for several hours.

  1. The page is not updated, just because the resource requested by the front end is old, and old for several reasons:
    • The code is not published
    • A cache resource is requested
    • The requested file is old
  2. Troubleshoot problems from the results of the reverse analysis, first find what resources are old, visit the pageLife-res.meizu.com/resources/l…, the request ofjsThe following resources

The document submission update is:

response

Life-res.meizu.com/resources/l…

On the whole, it is a handover problem on the surface (the original maintenance personnel have left). In fact, after encountering problems, we should learn how to find out the problems step by step from the performance. As mentioned above, we should analyze the problems step by step from the appearance of the results to find out the reasons for the further impact.