Thinking and summary of technical ability

One 、 The paradox of technological man's growth

There is a paradox in the programmer world that continues to confuse many technical people ： The confusion of people who are writing code is whether they will lose competitiveness by writing code all the time , Will it be replaced by young people who are more able to work overtime to write code . A typical representative is work 5 Core technical backbone of about years , It's time to start coding, but also to start planning the next stage of career development ; People who are not writing code are confused that I haven't written code for a long time （ Or less code ） Is my technical skills deteriorating , Will I still be competitive in the market , Is my development space limited . A typical representative is an architect or team with a business project Team Leader, They focus more on understanding and splitting business requirements , Management of team affairs .

This siege is very serious , It is a dilemma that technicians must face in the process of career development . But answer this question clearly , The root is not whether to write code or the amount of code , Its essence is to return to the root node of what is technical capability and how to improve technical capability . I summarize some of my observations and thoughts , For your reference .

Two 、 What is technical capability

To explain clearly what is technical capability, we have to see through the essence of technical capability , Analyze from the source . Select a few programmers' daily work problems for analysis and comparison , From our daily senses, identify which are technically capable practices , What are the practices without technical ability .

2.1  Repeat trivial work

One kind of work is to deal with the doubts of technical students in other groups about the business in the group , We call it daily Support . For example, ask the system you are responsible for what is the reason why an error is reported in the development environment that affects their project joint commissioning . The typical feature of this kind of work is , Someone may come to ask you questions at any time , It's also possible that different people ask you the same question many times . This kind of work is called repetition / Trivial work . Let's take a look at several ways to do this kind of work ：

• The first one is ： Take the matter on its merits , Answer this question. End . To this extent, you have only solved a specific problem . Unfortunately, many of our technical students are at this level .

• The second kind ： After answering this question, it will be sorted into documents , Write down the troubleshooting steps , Improve the work efficiency of yourself and your colleagues . To this extent, you see and solve the problem of internal efficiency .

• The third kind of ： Solidify the method and logic of troubleshooting into a small tool for the consulting students , So that he can check and solve it by himself in the future , This not only solves the problems of others, but also completely releases the efficiency of yourself and the same group . To this extent, you redefine the effectiveness problem and find a better way to improve efficiency .

• A fourth ： Find the root cause behind this problem , Find solutions from business principles or product functions . Abstract technical tools into the perfection of business functions . To this extent, it means that you have seen the rationality of the architecture from the simple technical improvement , And try to find a radical cure in business .

We can see these four different approaches , Even these repetitive trivial tasks , We can also extract value from the perspective of expanding the benefits , Then seek solutions at multiple levels . In the process of solving problems, they naturally exercise their multi-level thinking and abstract ability .

2.2  Abstract complex class work

Another kind of work is relatively abstract and complex work , Its typical characteristic is the need to only feel the phenomenon , It's hard to find the root cause , There is no clear goal and fixed solution , You need to make your own plans and Strategies . Take an example in practice , The problem of low efficiency of joint commissioning often occurs in complex system links , Every R & D student is complaining about all kinds of problems , But there is no way to cure . Faced with such a complex abstract problem , There are several ways ：

• The first one is ： Find the complaining classmate , Ask what the specific question is , And then targeted solutions .

• The second kind ： More extensive collection of questions , Then make a list , Classify and analyze and arrange the person in charge to follow up and solve , Finally, track progress regularly .

• The third kind of ： Deeply analyze the problems in the table and abstract the problems , Find the reason from the perspective of architecture tuning and product function , And find the business value brought by solving these problems , And determine the target disassembly path , Finally, advance and track the progress according to the task .

• A fourth ： Think about the relationship between this goal and the annual goal from a more holistic perspective , Relationship with organizational development , Think about how to expand the benefits of this , Think about how to exercise and train team students through the solution of these things .

You can see this abstract and complex work , In fact, there are many ways , If you look more carefully, you can see the tuning of the technical architecture , Look deep enough to match the target 、 The combination of organizational growth . Of course, there are also very general practices , That's pure single problem solving , Just become a project manager , Track progress through the task list .

3、 ... and 、 Hierarchical model of technical capability

Through the analysis of the above two kinds of daily work , We can clearly see that the characteristic of the practice with technical ability is that it can see the essence through the phenomenon , And it can optimize the technical architecture layer through the abstract induction of problems to solve similar problems .

So my definition of technical capability is ： Technical ability is an idea aiming at solving a certain problem 、 Methods and means of implementation , Its essence is the ability to solve problems . In programming , Is to abstract the business problems encountered 、 Refinement and logical construction , Through the development of tools to improve the efficiency of problem solving , Reduce manual inefficient repetitive work .

 If the methodology of using the definition of technical capability is right “ What is technical capability ” To analyze , Refined some models to express ：

The capability model is divided into three layers according to the step-by-step state stage ：

Technique , Hard core technology capability

In fact, this level of technology is more about hard core technology ability , It's basically the foundation of technology （ Such as computer foundation , Distributed technology , Quality awareness, etc ）. Although this is classified as a basic class , But this is also the foundation of technical people . Work 3-5 Students in are basically at this stage , That is, it takes a lot of practice to make your skills very skilled .

At this stage, the most important thing is to have technical curiosity , We should have technical expertise , Through the tempering of time, learn and Practice for a long time , Make yourself the core backbone of the team .



Law , Technical architecture capability

In fact, the level of law is more about the ability of technical architecture , That is to see through the essence through the phenomenon , Through the model 、 Principles to express essence to solve abstract complex class problems . This is a kind of high-level thinking structure , Basically 5-10 The student union in is at this stage . At this stage, more emphasis is placed on problem discovery , Problem definition , Problem analysis , Problem solving ability .

At this stage, we need to improve our cognitive ability , The essential qualities here are solid skin and inclusiveness , To accommodate different views and challenges . But there are also big misunderstandings at this stage , That is, it is very easy to be simplified to learn many methodologies or routines .

Avenue , Technology leadership

In fact, the level of Tao is more about technical leadership , That is to find vision and goals through technological influence , Lead the organization to achieve strategic results . At this stage, we should be based on deep technical architecture capability and technical hard core capability . Through technical thinking to solve problems beyond the field of pure technology , Generally speaking 10+ Students in will encounter such problems . The growth of this stage will also face the upgrading of people's bottom quality and ability , It requires more understanding than pure training and problem driven thinking . In fact, there are great misunderstandings at this stage , That is, many people only learn superficial Kung Fu without deep essentials , Pure becomes self-improvement , To others is PUA.

Four 、 How to improve technical capability

• Looking for the source of growth

People tend to take this issue lightly , I think growth is what everyone wants , But people haven't thought carefully about what promotes your growth ： It's you who want to enjoy this practice 、 thinking 、 The process of Enlightenment still Because I want to be recognized by the people around me / feedback / evaluation . These two may not feel much when you go well , But when you face failure in promotion , When the project is unfavorable and other setbacks, there will be great differences .

If you can find the source of your growth , Then when you encounter real difficulties and confusion, you can put your mind right , Look for a breakthrough , Get yourself out of trouble , Get considerable growth .

• Normalization summary and reflection

Whether it's the technical basis of coding, learning and growth , It is still a relatively abstract problem to solve , Or technical leadership growth . As long as it's growth , As long as we can grasp these two keys, we will succeed .

• The first is reflection , Be able to reflect on your shortcomings sensitively , Then constantly revise your mentality and behavior to make yourself degenerate .

• The second is to summarize , The process of summing up is to constantly sort out your own process , Confuse yourself , What is not is classified , And the more you sum up, you can make good use of the compound interest of time , The more you can promote growth .

Finding the source power solves the underlying motivation problem , Through summary and reflection, we can make use of the compound interest of time , Through these two mental methods, you can make yourself a person who can constantly enrich and improve yourself , To achieve this state, we must be able to become a strong technical person .



• Practical skills

We should make a normalized summary and reflection , The simplest technique is to write an article , Through the arrangement of words, you can make your thinking more mature , When you think more mature, you will naturally be able to speak more clearly to the outside world , If you can speak clearly, you can better share and communicate, and then you can really correct whether your ideas are correct . So I mentioned , Write instead of think , Think to promote , To test the truth Practical skills .

Reference material ：

1. WeChat official account （ Ali technology ）-《 Thinking and summarizing about technical ability 》