Programmers: The age of 30 that cannot be hurt

[[120972]]

Programmers work until they are 30, and finally make it from code slaves to white-collar workers, but they can no longer work and are always facing the risk of unemployment. 30 is an age that programmers cannot afford to lose. Where will they go tomorrow?

1. The 30-year-old phenomenon

In the officialdom, there used to be a 59-year-old phenomenon, that is, officials would try their best to make a fortune at the age of 59. It is obvious that power expires and if they don't make a fortune, they will retire and there will be no chance.

In the programmer community, there is also a 30-year-old phenomenon. Of course, if you have a stable job, such as working in a state-owned enterprise or government agency, you cannot understand the feelings of the grassroots working people. At the same time, congratulations on becoming a member of the system and being able to work until retirement without worries.

Everyone knows about the 30-year-old phenomenon, but it is not easy to give a definition. Here are a few manifestations that may resonate with you.

Facing a career bottleneck, I can’t write programs and it’s difficult to move up.

Salaries are higher, overtime is reduced, the younger generation is catching up with the older generation, and they are facing unemployment pressure; life pressure has increased dramatically, and they dare not change jobs;

The age limit for recruiting programmers is under 30 years old, which has become an unwritten rule in the industry, making it difficult to change jobs.

The 30-year-old phenomenon and the 59-year-old phenomenon seem to have nothing to do with each other, but they are actually due to the same reason: value depreciation. Officials are like emperors when they are in office. Once they retire, they become ordinary people, and it is natural for them to depreciate. The same is true for programmers. As the saying goes, "Thirty is the age of independence." Once they are around 30 years old, they face marriage and childbirth. On the one hand, they need a high salary to support their families, but on the other hand, they can't devote themselves to work as before, and the cost-effectiveness drops sharply. At the same time, a large number of cheap novices are pouring in, and they often use the latest technology. The older generation of programmers can only slowly stand aside.

2. Irreplaceability

When the 30-year-old phenomenon occurs, the only reason can be found in the programmers themselves.

Of course, we can also analyze from many aspects such as industry, society, government, and system to find deficiencies. These analyses may not be unreasonable, but they are certainly useless because we cannot change them. As the saying goes, "You can't blame the government for a hard life, and you can't blame society for a bad life." Looking for reasons from the outside will only make us complain and feel that we were born at the wrong time and feel depressed all day long.

Look for the reasons within yourself and try to ask yourself a few questions: "Why has my cost-effectiveness declined? Why did my boss hire me and give me a high salary? What determines a person's value?"

You may be able to list a very long answer, but I think it can be summarized in one sentence: "The value of a person is determined by his irreplaceability." Irreplaceability can be understood as the price you need to pay to replace your boss.

Because you are highly replaceable, your cost-effectiveness is reduced. On the contrary, because you are highly irreplaceable, your boss will pay you a high salary. Isn't that right?

Here is a short story:

When the technician retired, he warned his apprentice: "Talk less and do more."

Ten years later, the apprentice also became a technician. He found his master and said with a bitter face: "Master, I have always followed your instructions and worked hard, but those who are less skilled than me have been promoted and received salary increases, while I am still receiving the same salary as before."

The master thought for a moment and said, "Take a leave. If a light is always on, no one will notice it..."

The apprentice suddenly realized what was going on and really took a week off. When he returned to work, the factory manager found him and said he would give him a raise. It turned out that when he asked for leave, the factory manager found that the factory could no longer do without him.

The apprentice was very happy. He would take a few days off from time to time. Every time he took a leave, the factory manager would give him a raise. One day, the apprentice was about to go back to work after taking a leave, but the factory manager told him, "You don't have to come to work."

The apprentice went to the master in distress, and the master said, "I haven't finished what I said that day. A lamp can go out once in a while, but if it goes out all the time, its nature is different, because no one needs a lamp that is on and off from time to time."

In the story, the factory manager gave the apprentice a raise because he was irreplaceable; later, because other lights were on, he was replaced and the factory manager no longer needed him, so he was fired.

So in the final analysis, we still have to improve our irreplaceability. Otherwise, once the boss thinks that he can replace you at a lower price, you will face the risk of losing your job.

3. Where is the way out?

So how can programmers improve their irreplaceability when they reach the age of 30? Do we plan to be programmers for life? Where is the way forward?

As a veteran programmer, I think there are several directions to choose from:

(1) Become a technical expert

In fact, there is nothing wrong with being a programmer for life. What is important is that you must become an irreplaceable programmer, that is, you must become a technical master who can solve problems that ordinary programmers cannot solve. There are two versions of technical masters:

The first is the enhanced version of programmer. You are still a programmer, but you are a very good programmer. With years of accumulation, you are no longer an ordinary person in terms of the breadth and depth of knowledge. From assembly to Java, you are proficient in everything. You care about data structures and algorithms, have unique insights into system optimization, and are familiar with design patterns. You also have a complete toolbox and your own special class library. In fact, the enhanced version of programmers has very unique value. Unfortunately, it is rare in reality, because for any company, talent is always scarce. The boss's eyes are sharp. How could he turn a blind eye to a technical expert like you? Before you become a real master, you have already been appointed as a system architect, project manager or a higher position. Therefore, it is often impossible for you to keep your own piece of land and leisurely be your own master.

The second is the upgraded version of programmer. Although you are still a programmer at heart, your position has been upgraded to become a system analyst or system architect. This is a very natural and realistic choice. There is no gap between programmers and system analysts or architects. With just one step, you can drive from the rugged mountain road to the broad road. But this step is not easy. It takes several years of continuous thinking, learning, and practice to transform from a chrysalis into a butterfly.

(2) Become an industry expert

Industry experts are also an indispensable role in a company. They are familiar with the company's industry knowledge, business processes and details. Industry experts are generally not superhumans recruited from outside who only know business but not technology, but are often programmers who have grown up after years of hard work. As an industry expert who grew up from a programmer, you often also take on the role of system analyst. In the company, there are many people who have a general understanding of the business, but there are often few experts. For the next 30 years of your career, you must become an expert.

(3) Development towards management

The first step towards management is usually to be appointed as a project manager. In most IT companies, project manager is the smallest management position. You may not feel too much surprise, and your salary will not increase much, but this change can be said to be one of the most important changes in your life.

Don't underestimate project managers. Some people say that project managers are an ancient profession. Others say that the 21st century is the century of project management. In fact, project management has existed since human beings were organized. In the past, project managers might have been tribal leaders. A collective hunt or a siege could be considered a project. The knowledge of project management can be applied to all aspects of our lives, from the implementation of the moon landing plan to the organization of a family gathering.

An excellent project manager needs not only high IQ but also high EQ. It is no exaggeration to say that if you are competent in project management, you can be competent in all management positions at the tactical level, and even the quality of your family life will be improved to a new level.

However, it is not easy to become an excellent project manager. It can be said that it requires a certain amount of talent. Some people can learn without a teacher, but some people can never learn. Programmers are people with high IQ, but their EQ is often insufficient, which means that only a few programmers can grow into project managers. It is very rare for them to become excellent project managers.

If you think these aspects are suitable, then you have several options:

One is to live a down-to-earth life.

Employees who tell the truth, be honest people, do honest things, and get honest wages are very much needed by companies and generally will not face the fate of being fired; the second option is to change careers or start a business.

Because this industry is no longer suitable for you and there is no greater development prospect, you can only change your career. If you can change your career, it may not be a bad thing. Maybe in a new environment, you can inspire stronger energy and create a career. As for starting a business, it is even more challenging. It is recommended that you have become an excellent project manager before starting a business. Just imagine, if you can't turn a project around, how can you turn a company around?

Link to this article: http://my.oschina.net/u/1590538/blog/325779