Programmer's 35-year-old curse
When I was 35 years old, I had been a programmer for many years, but a mid-life crisis still found my door.
I found out that my salary was not as high as I thought it would be, and in this industry, the risk of losing my job was considerable.
Such a situation made me feel very anxious, and I began to reflect on my career and life values.
I started to think about what I really want and whether the hard work I have put in all these years is really worth it.
I started trying to find new career opportunities, and I started learning new skills in case I needed them.
The anxiety that comes with a mid-life crisis bothers me, as it does the times, but I believe that as long as I stay positive, I will be able to get through this.
35-year-old not to switch to management "to eat and wait to die"?
Where have all the programmers over 35 gone? People often issue such soul torture. Many people will choose to transition at the age of 35 to overcome the midlife crisis.
For programmers over the age of 35, it is a good choice to transform into a technical expert or technical manager.
Whether it is employment across industries or promotion to managerial positions within a previous industry, these options can enhance competitiveness and prospects for career advancement.
However, to be successful in these roles, one must have a love of technical work and a love of the industry, and be constantly learning and upgrading one's skill level.
In addition, understanding job requirements and conducting skills assessments are also very important.
It should be noted that not all programmers are suitable for management
If you are a programmer who loves technical work, then you must clarify your career goals and work hard for them.
Whether it's in a front-line role or a management role, as long as you have enough skills and enthusiasm, you can be successful.
In this context, there must be many programmers who are still writing code at the front line when they reach 35+. In fact, if you love technical work, even if you don't switch to management at the age of 35, sticking to the front-line position may not necessarily lead to poor development.
How to Break the 35-Year-Old Rule
The 35-year-old law is like a sword of Damocles hanging above the head, and the state of hanging but not falling is the most "tortured" person. But time is always ticking, and no one can avoid turning 35.
We are no longer young at this time, and technology may lag behind emerging technologies.
Faced with this problem, what we can do is to constantly learn and transform to adapt to the ever-changing public opinion environment and workplace ecology.
More importantly, there are some unfair phenomena in the IT industry, such as age discrimination and sex discrimination.
Therefore, the workplace ecology needs to be further improved. It is hoped that enterprises will create more fair and benign employment opportunities and employment environment for older technical personnel, and give older programmers a more inclusive and open space.
Programmers need lifelong learning
The IT industry is an industry where new technologies emerge in an endless stream. Many new languages, new frameworks, and new development concepts are born every year. The 20s are the golden age for learning new things, and the 35-year-old programmers are likely to be inferior to the younger generations in learning new technologies.
New technologies in the programmer industry are developing rapidly, and it can be said that they are changing with each passing day.
It is also for this reason that the midlife crisis has become a problem that we must face and overcome.
Think about a question: What extraordinary abilities do those programmers who can work to 45, 50, or even 60 have?
As far as my past experience and observations are concerned, I think: They have mastered some hard-core skills.
These hard-core skills help them overcome the disadvantages brought about by their age.
So what core skills do Android developers need to master ?
The following is the detailed learning resource document for the above skill map benchmarking:
Therefore, if you usually only know how to work hard, or are too stubborn about a certain implementation detail, and have not looked up at these technologies, then it is necessary to sort out the Android knowledge system before preparing for the interview, so that you can win a satisfactory Offer .
Compared with the fragmented content we usually read, the knowledge points of this note are more systematic, easier to understand and remember, and are arranged strictly according to the knowledge system.
Full set of video materials:
1. Interview collection
2. Source code analysis collection
3. The collection of open source frameworks
welcomes everyone to support with one click and three links. If you need the information in the article, just click the CSDN official certification WeChat card at the end of the article to get it for free↓↓↓
