3. Summary of technical Accumulation

1. What is technical accumulation?

What is accumulation? In fact, it is very simple to create a project or a different business module of the same project. How many business modules can be used directly and can be used for reference directly. From the perspective of the company's business systems, there are many things in each business, such as user management, permission system, printing function, query function, report function, approval process, home page, etc, after the company has been working on these projects for 10 years, it should be able to greatly reduce project development without having to study any new project, free up more energy to cope with business problems. But there is no doubt that our technical accumulation is poor, basically in the personal brain.

2. Technical Accumulation

Why is there nothing that can be reused after ten years of technical accumulation? Even if there is one, it is also the experience of each person. Because our accumulated ideas have always been wrong. We always think that reuse is to encapsulate a function and encapsulate it for others to use it. The result is a closed thing, without a steady stream of fresh external content, it is impossible to grow or even mature.

We constantly "create wheels" in every project, and often we have to first find out whether the wheels are round or square. 4. When we changed the process control in March May, I felt sad and sad. Why is there no technical accumulation in zhongzhi for ten years? Which project does not require process control?

Among all the basic functions, user permission management is a good accumulation. Then we can follow up on it. The reason is very simple, because it is open-source, all projects use the method of directly copying the source code (even if the source code cannot be copied directly due to the technical architecture, the requirement is completely inherited), and the modifications are made based on the requirements. Therefore, we can see that all the unmodifiable items after encapsulation are scolded, difficult to use, and never improved. However, it is a pity that the last step of user permission management is not well done, that is, to summarize the requirements of all projects and maintain them as a version that is continuously improved and unified control. This must be done at the company level. This is the true technical accumulation of the company.The accumulation of technology is not a technical thing, but a management thing.

3. Internal open-source plan

The accumulation of technology is not to form a control or platform that is encapsulated and difficult to modify, but to form a clear and growing source code pool and technical understanding based on the source code pool. The "internal open-source" plan is proposed as follows:

① Build the source code pool and assign a dedicated person to manage the version by function module.

② All the project development needs to use the corresponding functional modules, which will be temporarily assisted by a specialist in the source code pool based on the latest version of the existing source code pool.

③ After the new source code of the Project is formed, a dedicated person will assist the regression source code pool to form a new version.

④ Each function module of the source code pool will be applied in multiple projects and will be gradually improved to maturity.

For example, the permission system function required by each system is managed by Michael Jacob in the source code pool. During the construction of a new project, James temporarily calls and coordinates the new project to adopt the latest source code and functions of the permission system in the source pool. The project team makes adjustments based on the actual needs of the project. With the source code, the project team will be very flexible to adjust, and the original functions and new features can be improved based on actual needs. After the permission system function is built, Michael Jacob coordinates and merges the new source code into the source code pool to form a new version.

The technology here not only refers to program development, but also to interface art and product design.