Recently, companies such as Huawei, Alibaba and Tencent have tightened the threshold of external recruitment. Some are even saying that many places have stopped hiring in response to the economic downturn. Huawei also publicly announced that it would fire its technical staff over the age of 35, causing a large number of older programmers to panic and anxiety. Now many people say that making technology is youth rice, many people do not do 35 years old. So is 35 really a hurdle for programmers?

First of all, in my opinion, the answer is no. Nowadays, the career life cycle of programmers has been significantly extended. As the software industry continues to mature, programmers will gradually become a lifelong career. There are a lot of 35-year-old peers around, but in fact, many of them don’t write code any more. Some of them have changed their business, some of them are still in the development position, and most of them are management oriented, and most of them do code review. But there are those who insist on writing code.

There are several reasons why many programmers stop working in r&d after the age of 35:

First: Software development jobs are stressful. The working pressure of programmers is generally high, especially in Internet companies. The development cycle of many projects is often short, and overtime is common in the field of software development, which is an important reason for programmers to choose transition when they are older.

Second: programmer’s knowledge structure update speed is fast. Programmers not only have to bear great work pressure, but also face the problem of updating knowledge structure, which leads to programmers in busy work have to take out a certain amount of time for independent learning, which is a double test to programmers’ working ability and learning ability. Many programmers in the old knowledge structure has not been updated in time, naturally will be gradually eliminated.

Third: promotion. Due to the rapid development of The Internet in China, the speed of talent cultivation obviously fails to keep pace with the development of the industry. Therefore, many programmers are generally employed in management positions after the age of 35, in order to cultivate more professional development talents. This is also a common situation.

After 35 years old (should be earlier), in fact, it is inevitable to lead new people, lead projects, these are more energy. But I think as long as you’re in a technical position, you still have to write code and be sensitive to code. If you really do not write a line of code, even can not write, and as a technical department leadership, I believe that you are also difficult to convince the public.

In the early stage of China’s software industry, there were a large number of low-level software outsourcing services. The technical content of these outsourcing tasks was generally not high, but the workload was very large and the cycle was tense, which led to many programmers leaving their jobs prematurely.

With the structural upgrading of China’s software industry as a whole, there will be more and more demand for R&D programmers in the whole scientific and technological field in the future, and the career life cycle of R&D programmers will be greatly improved compared with the traditional application level programmers, so the overall career life cycle of programmers will be improved in the future.

Therefore, the age of 35 is the past for programmers, can not be generalized, many people before the age of 30 ready to transfer from technology to management, business, pre-sales, operation and maintenance, so as a technical programmer’s development direction is still very complete, but to learn to accumulate, can not consider these in the present. 35 years old is not can not be a programmer, but your ability to adapt to overtime, energy will be less than young graduates, so to be good at a certain direction.

Having said that, let’s take a look at some of the major technologies out there, which I’ve broken down into six parts:

Architect Fundamentals

Framework source code reading

High-performance Architecture

Micro service

Team collaboration

Actual Practice of Mall Project