There has always been a curse in programmer circles: the 35-year-old midlife crisis.
The energy and physical strength of 35-year-old programmers will inevitably decline, they say;
They say that the rich experience of 35-year-old programmers is not as popular as the innovative energy of younger employees;
They say 35-year-old programmers will face increasingly narrow career paths and increasingly complex social pressures.
These "legends" make many programmers feel more anxious with each step closer to turning 35, and eager to find a way to break the curse.
35 years old, is it really the line of prosperity and decline in the workplace?
Some time ago, I saw this post on Zhihu: 35 years old seems to have become the line of prosperity and decline in the workplace. The unemployment risk superimposed on the mid-life crisis aggravates anxiety. What do you think of the "35-year-old crisis"? , Sometimes you don’t need to be eliminated by the society, and you feel that your physical strength can’t keep up, especially for Internet companies. The developers are 35 years old or even less than 35 years old, and many people generally change careers or leave passively.
(PS: Don't sell anxiety here)
We need to look at it with the right perspective:
1. The culture of some Internet companies is like this. For example, some Internet companies basically do not recruit people over the age of 35, and they will gradually reduce or eliminate old employees;
2. The technology can't keep up, or the technology is relatively weak, are there any people who try to improve themselves;
3. People who eat and drink, do not listen to discipline, and have not made actual contributions to the company;
4. The company's financial situation is in crisis. Some people have to be eliminated, and some core people are retained. Others will be eliminated even if they have good technology or are more advanced. This is not too high. If this kind of problem occurs, make plans as soon as possible. I think As for the reason why many companies eliminate 35-year-olds, most of them are among the above situations. What I want to say is that 35-year-olds are not scary. What is scary is that you are lazy and mediocre before the age of 35.
How to deal with the "mid-life crisis" in the Internet industry
1. Pure technical route
2. Mixing circles, mixing with people, relying on internal push
3. Rely on headhunting
4. Rely on yourself
Improving your abilities is a very, very important part. In addition, it should be noted that when you study by yourself, you must have a direction. On the one hand, you must improve your reputation and make your resume shine. On the other hand, you must study deeply and have real skills.
Always keep a peaceful mind
I have seen a post like this before: What kind of programmers are still rushing by companies after the age of 35?
As for how to not be eliminated at the age of 35, then the above post has already given the answer, here are some suggestions for you:
1. Whether you are 30 years old or 35 years old now, I hope you can maintain a progressive heart and always maintain a sense of crisis
2. Those who are technical can go deep in a certain technical direction. If they can't get through, they can go to management. If they can't go through management, they can go to products. If products can't go well, they can go to lecturers. The same, as long as you can survive and make money, other industries can still choose
3. Now the retirement age has been delayed. Girls are 60 and boys are 65. Now you have a lot of time to choose from around your 30s. Even if you start a new industry again, although the previous few years may have been a low ebb, I personally feel it. It is also necessary to say an extra word at the end: no matter what kind of work you are doing now, please be sure to maintain a strong physique, because having a good body is really important!
In my opinion, self-knowledge and continuous improvement of experience are very important.
No matter how busy I am, every day I take an hour or so to read a book. We have a group of authors, and the high-quality authors in it also study frequently. Sometimes, although we are also cut off, it is worth learning a little something. Look at the excellent people around you, there is no one who does not study.
In order to help everyone improve, this document has been specially prepared. The summary covers a wide range of content, including 14 technology stacks (for the full version, see the free method at the end of the article):
- Basics
- JVM articles
- Multithreading & Concurrency
- Spring articles
- MyBatis articles
- Spring Boot 篇
- MySQL articles
- Redis articles
- Spring Cloud articles
- Nginx articles
- MQ articles
- Data Structures and Algorithms
- Linux articles
- resume
Part 1: Basics
Article 2: JVM Articles
Part 3: Multithreading & Concurrency
Part 4: Spring
Article 5: MyBatis Articles
Part 6: Spring Boot
Part 7: MySQL
Chapter 8: Redis Articles
Chapter 9: Spring Cloud
Chapter 10: Nginx
Chapter 11: MQ Articles
Chapter 12: Data Structures and Algorithms
Part 13: Linux
Chapter 14: Resume
finally
The entire document has a total of nearly 200 pages. It is definitely unrealistic to show all of them. In order not to affect everyone's reading experience, only part of the content is shown. Find a good job and save everyone's time searching for information on the Internet to learn! For those who need it, click on the business card at the end of the article and scan the code to get it for free.