How to become a good technical manager? You have to do these three points (3) Technical planning and management

Preface

System health inspection

Why put system health inspection into technical management? I think this is a very important link. The traditional aviation, electric power, and automobile industries must have a certain inspection mechanism to ensure the normal operation of the equipment system, and the software system also needs an inspection mechanism to ensure the healthy development of the business.

With the continuous development of business and the continuous increase of business volume and data volume, the corrosion of the system architecture is unavoidable. In order to ensure the health of the system, it is necessary to continuously consider the optimization of the system architecture and performance.

System monitoring and alarms can find problems in the system to a certain extent. Some hidden dangers in the system need to be discovered through inspections of the system. If the optimization is not timely, it will cause failures in extreme situations. The granularity of inspections is recommended to inspect yourself once a week The business system in charge.

The system inspection focuses on the following points:
● System indicators: whether the system CPU, load, memory, network, and disk have abnormal fluctuations, and confirm whether it is caused by the release or the system call is abnormal.
● Slow interface: Generally, interfaces with rt greater than 3s need to be paid attention to. Extreme concurrency scenarios may easily lead to an avalanche of the entire system.
● Slow query: MYSQL slow query requires special attention. As the amount of data increases, slow query needs to be optimized.
● Error log: Use the error log to find some hidden bugs in the system to prevent these bugs from being enlarged and even lead to malfunctions in extreme cases.

Technical planning

Technical planning is usually the responsibility of the team’s TL. TL needs to think about the technical optimization plan for each quarter from the perspective of the overall situation in each fiscal year to repay technical debt. Technical debt also has interest. Because of the existence of interest, technical debt is not timely If it is repaid, it will show a nonlinear growth in the future, causing unexpected losses.
The technical plan here includes the following points:
● Architectural optimization: Some code with poor structure, low cohesion and high coupling will make it impossible to start even minor changes in requirements or function extensions, and the cost of modification is likely to exceed the cost of rewriting. cost. Similarly, the coupling between systems also needs to be focused on. Following the principle of microservices, the system should also follow the principle of single responsibility. For systems with unclear responsibilities, perform decoupling and optimization, and carry out some modular transformations, service isolation, and public services. abstract.
● Performance optimization: Based on the fiscal year's development assessment of business volume and data volume, according to the current QPS\RT of the system service, some upgrade strategies for system performance need to be planned in advance, including focusing on the optimization of some slow interfaces and slow queries.
● Resilience and reliability: The services provided by the system need to guarantee data consistency, idempotence, and anti-heavy attacks. At the same time, it is also necessary to consider what problems exist from the perspective of fuse degradation and multiple activities in different places, and whether the current system SLA indicators can be reached High availability, what optimization needs to be done to ensure the high availability of the system.
● Scalability: Whether the application service is guaranteed to be stateless, and key nodes can be quickly transferred and expanded in the event of a failure to avoid the expansion of failures.

to sum up

What qualities should technical TL possess?

First of all, technology serves the business after all, unless technology is the business itself and must reflect its commercial value. In many companies, technology research and development has really become a tool to achieve the needs of other departments. I think such a technology TL must be unqualified. First of all, it cannot affect business development. The demand proposer will undergo a lot of transformations. If the demand is not passed on without thinking, the whole process will be distorted.

Second, I think the most important thing is the ability of architecture design, and perhaps the ability of management is second. For management ability, I think the most important thing is the ability to perceive the team, because once you reach the level of technical TL, you can't get too far away from the front line, business details can be unclear, and the general direction must be clear. Without very delicate perception, many decisions will be biased.

If he is not a business architect, or someone who can point the team in a better direction, he will eventually become a requirements translator, and the product manager will do whatever he says. He was more responsible for ensuring the quality of the product and the speed of development, and was eventually dismembered into a very trivial person. Once the team has reached a certain scale, the team will move from pure demand realization to team operation, and operation needs direction. Business architecture is a comprehensive capability based on operations and data.

Regarding the technical aspect, technical TL needs to possess the following qualities:
● Good technical vision, excellent problem-solving ability and architecture design ability.
Technical TL needs to have a good technical vision and does not need to be proficient in all kinds of technologies, but it must be all involved and understood, and a good understanding of the development trends of various technical fields and the application scenarios of mainstream non-mainstream technologies. Know what technology to use in what scenario, what scale of business development, and what technical reserves should be made in advance.

The design of product architecture must be flexible enough to not only ensure the high efficiency of current development, but also leave room for expansion for the evolution of future product architecture.

● Strong hands-on ability and excellent learning ability.
Technical TL does not need to write the code by yourself, but if necessary, you can participate in the first-line coding work at any time. Technical TL cannot stay away from the front-line work for a long time, let go of martial arts, and talk on paper. Otherwise, if things go on like this, serious mistakes will be made in technical judgments. In addition, a technical TL should also be a person with very good learning ability. After all, the technology upgrade in the IT industry is very fast. If you do not have the ability to learn quickly, you are not qualified to be a technical TL.
In addition to managing people and affairs, technical TL has many other things to do, including establishing team R&D culture, team talent training and construction, cross-departmental coordination and communication, etc., so that technical TL also requires good communication and Management ability.

supplement

How to become a good technical manager? You have to do these three points (1) Development specifications

How to become a good technical manager? You have to do these three points (two) development process

Guess you like

Origin blog.csdn.net/qq_46914021/article/details/109259260