Code of Conduct for Firefighters

Introduction
After going up the mountain for a long time, I always encounter tigers. After working for a long time, I can always send away a few old colleagues, and then inherit their legacy and take over their projects.If you were originally in the same project team, it’s okay, but the most fearful thing is that this project is the only intersection between you.However, as an almighty code farmer, the leader asks, "How long will it take to take over?", we will still say without hesitation: "One month, guarantee to complete the task", if the leader frowns, "Actually working overtime, two weeks willCan".

Question
How should we quickly take over an unfamiliar project?

Project
Our project consists of two parts, business + code.The reason why we put the business in front of the code, yes, we need to understand the current business first. Only by understanding the business can we know whether what we are doing right now, including the implementation of our code and the correctness of subsequent problems.

The business consists of two parts, the business of the own system itself and the business of the upstream and downstream related systems.For your own system business, products and operations are the best help, and they can help you quickly grasp the core of your business.However, there are differences between the two. The product can summarize the specific implementation of each business scenario, and the operation can inform them of their daily work and the core points of concern.For the system that has just taken over, clearly understanding the key points is obviously the most important.

For upstream and downstream related system business, we only need to understand what they do and how the systems interact in the early stage.It is recommended to sort out the input and output content between related systems, which will help improve your control over the system.

Code, before entering the sea of ​​codes, the first thing we have to do is to pray to the Buddha that the predecessor is a kind person, because kindness can produce wisdom, and wisdom can allow him to write kind codes.However, in practice, when taking over an old project, the old code is not so important. The reason why we need to look at the old code is because we need to maintain the old system functions.However, after the previous business sorting, you can already know which core functions of the entire system are, so there are not many codes that need to be deeply understood.

Is the above the most important point in the question of how to take over a project?Yes and no!For a system, our most basic requirement is normal operation.Inexplicable problems may occur in any system every day, and these problems, for an old system, obviously will not be the first time, and the problem handling obviously has a fixed pattern, so in the work handover, should be required.The ex leaves a plan for dealing with everyday problems.As for how to get the ex into submission, the Eight Immortals have crossed the sea.

After the above series of operations, I believe that it is not too difficult to basically control a system in two weeks.As for the follow-up full integration into the project, it needs to be driven by business requirements. Only by repeatedly tempering in the requirements can we achieve the realm of the unity of man and system.

by Jiang Pei