If technology transfers to management is it necessary to lose technology
Many technical managers have this kind of confusion. We do technical management, and the time to write code is getting less and less, and the hands are getting rustier and rustier, but it seems to be a very contradictory thing to participate in more technical reviews and technical decisions.If technology transfers to management is it necessary to lose technology
If technology transfers to management is it necessary to lose technology If technology transfers to management is it necessary to lose technology If technology transfers to management is it necessary to lose technology If technology transfers to management is it necessary to lose technology
Therefore, they often feel very anxious, their technical ability is getting worse and worse, their daily management work is very trivial, and there is no time to improve their skills, will one day be older, lose value or cost performance, and be eliminated by the industry.
In fact, there are two problems here. First, what is the core competence of technical managers; second, what is the difference between the technical capabilities of technical engineers and technical managers?
Let me talk about the first question, what is the core competence of technical managers. To be honest, this is also a problem that has plagued the author. Until one of the MBA courses, a sentence of the professor made the author clear.
“What is the core competence of a manager? It is professional judgment.”
In 2013, Zhang Yong of Alibaba saw the future of mobile Internet and proposed “All in Mobile” to help Ali successfully get the first class in the mobile Internet era. This is professional judgment.
Haier Zhang Ruimin, when the Internet era came, he proposed the “rendanheyi” model, “revolution of one’s own destiny”, and the enterprise was reborn; in the era of entrepreneurship, he proposed the “maker model” to turn the enterprise into a creative enterprise. The customer platform unleashes the innovative power of the enterprise. This is also professional judgment.
In the same way, the core competence of a technical manager is technical judgment. To put it simply, technical judgment means “do you want to do” a certain technical project, “can it be realized” if you want to do it, whether it is suitable for doing it now, and also consider technical risks, project management complexity, cost, etc., which are far beyond The scope of writing code.
If technology transfers to management is it necessary to lose technology If technology transfers to management is it necessary to lose technology If technology transfers to management is it necessary to lose technology If technology transfers to management is it necessary to lose technology If technology transfers to management is it necessary to lose technology
Technical capabilities of engineers and technical managers
What’s the difference?
The second question is, what is the difference between the technical capabilities of technical engineers and technical managers? Simply put, the technical ability of a technical engineer is to write code and make specific technical implementations. The technical ability of a technical manager is technical judgment, a technical decision-making ability cultivated through long-term accumulation in technical and non-technical fields.
Many friends have always confused the technical capabilities of technical engineers with those of technical managers. It is ridiculous to discuss whether the technical director should write code.
This depends on scenarios. For example, the entrepreneurial team lacks resources. Of course, the technical leader must do everything by himself and write code by hand, but when the team grows slowly, the technical leader must focus on making technical decisions.
That is to say, it depends on the stage and size of the team, as well as the role of the technical leader, to determine whether his work is to be a technical realization, technical decision-making, or a combination of both. Whether the technical director or CTO writes code or not, it does not make any sense to leave the discussion of the specific scenario.
Technical judgment, what are the things to judge?
Technical judgment is mainly reflected in three aspects:
First, the judgment of the result.
That is, whether to do or not to do this thing, what kind of indicators are used to measure it’s good or bad, for example, if a developer proposes to use Flutter to refactor an existing app, the technical manager must give a judgment to do or not to do it.
The starting point for technical personnel to consider this proposal may be to “play with” new technologies and add points to their resumes. As a technical manager, they consider what is the key issue of the company’s App at this stage, if it is the stability of the App , The development speed is not fast enough, so as a new technology framework, can Flutter solve the existing problems? If not, then it may not be the best time to introduce it now. One or two technicians can be arranged to do pre-research and start paying attention to this technology.
It is not difficult to find that technical engineers and technical managers have very different perspectives and dimensions of thinking about the same problem.
Second, the judgment of technical solutions.
That is to judge the technical feasibility, maintainability, cost-benefit, etc., and usually, guide the team in the technical plan review process.
For example, whether the solution is technically scalable, whether it can establish technical barriers for the company, whether there are detailed log records in the technical framework, whether there is an early warning when an online failure occurs, and provide detailed error logs for analysis and selection of this technology How about the opportunity cost?
The so-called opportunity cost means that if you choose this technology, you will give up another technology. Is it possible that another technology has greater benefits?
Technical managers also think more deeply and comprehensively about technical solutions than technical engineers. Technical engineers may only consider whether they will be implemented, while technical managers must ensure that there is no major deviation in the direction.
If technology transfers to management is it necessary to lose technology If technology transfers to management is it necessary to lose technology
Third, the judgment of risk.
Including technical risks, project execution risks, team risks, etc. Technical managers use their own experience, thinking analysis, team discussion and other means to identify the main risks and take measures to avoid them.
The technical review, project review, technical plan planning, and other work that technical managers usually do is to make technical judgments, and technical ability has not deteriorated, because as technical managers, technical judgment has been continuously exercised and improved in daily work.
How to improve technical judgment?
The technical judgment of new technical managers mainly comes from the previous experience of writing code and doing projects. At this time, knowledge transfer must be done to convert the cognition of the technical engineer’s experience into the cognition of the technical judgment of the technical manager.
There are four main aspects to the improvement of technical judgment:
First, the team’s daily technical and product work report. When the team reports on the progress of technology and products, it is a good time to obtain information feedback and verify technical judgments, to see what impact their previous technical decisions have, whether there are areas that need to be adjusted, and to learn the thinking and experience of their subordinates, Update your own technology and product knowledge in a timely manner.
Second, participate in the review of technical solutions. Participate as much as possible in every code review, as large as the overall system plan review, especially the overall architecture review of large systems. This is the best opportunity to systematically improve technical judgment. The architect’s explanation, including the logic of the architecture design, The characteristics of each technology, etc., combined with their own understanding and experience to provide feedback to the team, the ability to judge the structure can also be improved.
Third, preside over the top-level design and planning of the system. The technical manager can directly assume or preside over the top-level design and planning of the system, the business architecture planning, the division of the system layers, the data exchange agreement between the subsystems, the selection of the technical framework, the system capacity planning, etc., to control from the overall technical architecture, Then the team will further develop and make more detailed planning.
Fourth, continue to learn new technologies. Engaging in technology management does not mean that technology is completely discarded, but most of the code work is abandoned, but the learning of new technologies cannot be stopped, such as the technical framework of artificial intelligence, several models of machine learning, and what problems they are good at solving, etc..
Another example is the characteristics, implementation principles, encryption algorithms, and differences in accounting methods of several blockchain consensus algorithms. The focus is on what problems this technology solves, the principles and mechanisms of implementation, rather than how to skillfully use this new technology. Hello World”, of course, writing some demos is necessary to deepen your understanding.