CTO will teach you: how to take over his project when a technician suddenly leaves

Technical personnel , The most discussed and feared , Nothing is better than taking over others' projects 、 Maintain legacy projects of history . Especially those without any documentation 、 There's no handover 、 Projects without human collaboration . It's painful and sour , It's really “ Like drinking water , affair ”.

Today, let's share some tips and tools , Teach you when facing the sudden resignation of technical personnel , How to quickly take over his project . Reduce the pain of taking over and maintenance .

Pull the code , Run locally

First , Open it first git Permissions for the code warehouse , Pull and check out the corresponding code warehouse locally . Usually a product / A project , There is more than one code warehouse . then , Start running locally .

If there is no deployment document for the project , It's estimated that you'll have to deal with it . Because a system starts normally , Need to be solved ：

1、 Installation of language versions and dependent packages ： For example PHP 5.6 still PHP7, yes Java 7 still Java 18, yes js still nodejs still ES6 still ts？ secondly , use composer Install well PHP Of vendor Catalog package , Or use npm/cnpm/yarn according to package.json Install well node_modules, Or use maven/ant Install well JAVA Of SDK Bag, etc . then , These are still very basic , Very common .

2、 Then install the necessary database locally , for example MySQL、MongoDB、Oracle; Start the necessary services , for example ： queue 、 Scheduled tasks ; And the system interfaces and services behind it .

3、 Get the previously available test account , Log in .

Be familiar with the operation and process of launching

After the project can run normally locally , You can try it , Modify some simple copy , Or not modify , Be familiar with and operate the process of launching the project . Because you don't know when , We need to fix a fault immediately and then release it online .

Get familiar with the release in advance , Drill operation , It is necessary to plan ahead .

Know in advance , Publishing is manual , Package and compress, then upload and decompress ; Or through the interface operation of the publishing system ; Or through Jenkins、Docker、k8s And other tool systems .

Also know in advance , What are the pitfalls and precautions of the press conference , Once the release fails , Online services cannot work properly , It will be a great disaster .

Familiar with the product 、 Familiar with the business 、 Familiar with technology

Take over an old project , The first point is ： Get familiar with your products as soon as possible . What are the specific main functions of this product ？ For whom ？ Who is the customer group ？ How many users are currently registered and used ？ Who is the upstream supplier ？ What are the other members of the project team ？ Etc. the background information of these projects and products should be clear .

The second important point ： Get familiar with the business as soon as possible . Business is critical , You should have a certain understanding and learning about the industry of the product you take over . That is, what we usually call business in a specific field . This business is to do e-commerce 、 Or advertising 、 Or playing games 、 Or do ToB System integration , Terms and knowledge in different fields are also different .

The third point ： Quickly understand the technology stack used in the current project 、 programing language 、 Development framework 、 database 、 Environmental requirements, etc . Technology is the foundation .

Document and save relevant link accounts

Good memory, bad pen .

In the process of taking over the project , There will be a lot of information 、 Knowledge and configuration information , Use the right tools , Record the whole process , Collect and record key 、 Valuable information .

stay YesDev, You can create a project , Make overall records and collaboration .

for example , stay 【 link 】 Can record items in Git Code warehouse 、 Before Tower Handover link 、 Reference and Baidu to CSDN Learning materials, etc .

Start to fix some problems and work orders

In limine , From some small problems 、 Small Bug Start with the work order , Through some questions , Check some pages , At the same time, do a good job in common database query statements SQL、 Internal scripting tools 、 Record and familiarity with perceived problems .

When recording work orders , Contact information of users 、 Screenshot of the page 、 link 、 Code location 、 Database query, etc , Collect . It is convenient to encounter similar problems in the future , There is information to check 、 There is knowledge to learn .

Start developing some small requirements and functions

When you start developing new requirements , Don't worry about changing the code .

because , You'll find that , Writing code is simple , But write 100% Code that conforms to the original business logic and rules is difficult .

in other words , The code syntax of a programming language is not difficult , The difficulty lies in completely understanding and mastering the business logic of the original code .

So , You can use ProcessOn、Xmind、Viso Online tools or local software , First, I'll sort out the thinking map of current products and technologies 、 Sequence diagram of core business logic 、 Swimlane diagram of the overall business process 、 Architecture diagram of the current system . At least these four figures can be combed .

for example , Sort out the thinking brain map of product functions , Help you understand the function and form of the product . By clicking on 、 Browse 、 Experience and use every page of the product , You can comb while operating . For example, I combed the products of the open platform of the interface master .

then , Open local IDE Code editor , Find the source code behind the corresponding page and interface , Go to the bottom 、 At the core 、 above all 、 The most complex code module , Browse the source code 、 While sorting out the sequence diagram of the core . This piece of work , It allows you to grasp the underlying essence and core of the project , Familiar with the original code style 、 Programming paradigm 、 Design patterns 、 High concurrency processing 、 Dependencies of each module . for example PhalApi The core sequence diagram of the open source interface framework .

The third picture , It is the swimlane diagram of the overall business . It can let you know the upstream and downstream data flow of the overall system 、 The underlying dependent systems and network links . When something goes wrong with your system , You know who to call . for example , For the process of live broadcast group mall .

The last part is the system architecture diagram for technology architecture . This part , You can go through nginx Diary 、 Or the service opened by Alibaba 、 And the information recorded internally to find out which third-party interfaces your system calls . For example, which SMS interface is used ？ Did you use OSS Object storage ？CDN What was used ？ Does the database use cloud services or self built ？ You should clearly know how many servers there are at present , How to deploy and call each other , What is the network link . Start with the user requesting to open the page , What does the system do behind it ？

so to speak , When taking over others' projects , You should at least organize and draw four pictures by yourself ：

**1、 Product brain map ：** Help you understand the function of the product ;

**2、UML Sequence diagram ：** Help you realize the core technology of source code ;

**3、 Overall business swimlane diagram ：** Help you get familiar with the business process as a whole ;

**4、 System architecture diagram ：** Help you master the current server deployment and network links .

https://mp.weixin.qq.com/mp/appmsgalbum?__biz=MzIxMzUzOTIyNg==&action=getalbum&album_id=2488777964401999873&scene=173&from_msgid=2247493926&from_itemidx=1&count=3&nolastread=1#wechat_redirect