Thoughts on winter

At the beginning of 2019, there is a saying “Three gold, four silver”. I don’t know if you’re in a panic at this point. Because the winter of 2018 was cold. In fact, 18 years of cold is not a very long time, and I did not put on a military coat. But the sudden Internet winter affected many people, of course, the Internet winter is mainly affected by the programmer.

In retrospect, 2017 was the year of the rapid development of Internet, Shared economic achievements just a concept of how many companies, a variety of Shared cycling, late in 2018, however, like all of the situation has changed, you will find all the Internet practitioners in yell, Internet winter has come, the prostitution in Meituan, Meituan’s massive layoff triggered a flood of job postings, while netease, Didi, IQiyi, JINGdong and other strong enterprises in their respective fields are also laying off employees. In addition, relatively small companies such as Zhihu, Smartisan technology, Douyu and other enterprises have also carried out varying degrees of layoffs, not to mention those smaller Internet companies, all kinds of bankruptcy, bankruptcy, no wages.

As these companies lay off employees, most of whom are programmers, they trickle back into the job market. But how many companies can take them? You should know that there are not only those who are getting laid off but also those who are leaving voluntarily to “move to a bigger platform.” Thousands of armies and horses cross the river, why do enterprises choose you in the cold winter, between you and him is their own strength, then some people are confident and some people are flustered.

I have three or five years of work experience, but the salary and position level are very different. It is really hard to find someone younger than me as my leader when I enter a new company.

This kind of situation, let the year ready to leave the people also hesitate a lot, after all, stable career can solve the livelihood, job-hopping is not good to jump into the pit can not be beautiful, also let a lot of people hold a wait-and-see attitude, because do not know what market is outside now, so naked resignation is firmly not recommended, unless you are confident enough.

Universal phenomenon

In the cold winter of the Internet, competent people have nothing to fear. In the 21st century, after all, talent is the core of development. If programmers’ salary wants to increase greatly in a short time, they can only achieve it through job-hopping. However, many people are still afraid to try it easily. Although job-hopping can raise high salary, it is also related to their own ability, which is accumulated from previous work.

It is a common phenomenon in the programmer industry that salary is not closely related to years of service. In other industries, the longer you work, the more seniority and experience you have, the higher the position and the higher the salary. However, the programmer industry is different. In the programmer profession, there is a big salary difference between the same years of work. A person with five years of work may earn less than a person with three years of work, and a person with three years of work may lead a person with five years of work in a group.

Think about it. Why does this happen? Why are you the tragic one, while others are the straight ones? Very upset but also want to think about why. In fact, it is closely related to the attitude of meeting the bottleneck period and dealing with the bottleneck problems.

Bottle neck: the neck of a bottle that is wide at the bottom and narrow at the top. The contents of the bottle have to be emptied out of the bottle. “Bottleneck” is generally used to describe the stagnant state encountered in career development. This stage is like the neck of the bottle, which is a pass. If you do not find the right direction, you may be trapped in the bottleneck.

The bottleneck period of programmers varies from person to person. Most of them may have their own technical bottleneck in about 5 years of work, and some of them may have their own bottleneck period in about 3 years from a high starting point. In the bottleneck period, some continue to dig deep technology but little effect, while some have no choice but to try to transition into management or products, there should be but few of them.

Bottleneck period performance is: the new technology does not move, THE original technology I understand and skilled use, but only a little understanding. You’re good at your job but you suck at an interview.

Bottleneck of reason

Why is there a bottleneck? IT is often said that the IT industry is a constant learning industry, and programmers need to have a sharp nose for new technologies. They all say, “After 30, I’m too old to learn.” If you’re just coding you need to be logical and mentally active. In fact, age is just an objective factor, technology is constantly updated, yes, 30 years old brain can not remember the young also true. But this is just an objective external factor.

Programmers should start with 30. You can’t learn technology at 30 and still learn the way you did when you were young. Watch video, need teacher to teach, classmate to give directions. Programmers should have their own skill pool by the time they’re 30, so learning new skills can be a very similar attitude.

The Song Dynasty Zen master Aohara Xingsi proposed three levels of life: at the beginning of meditation, see mountains are mountains, see water is water; Zen enlightenment, see mountains are not mountains, see water is not water; Enlightenment in Zen, see the mountains are still mountains, see the water is still water. So how should we understand the meaning of these three states?

Programmer learning technology should also be such a three-stage process, 30 years old maybe you have not reached enlightenment, but certainly to achieve the realm of enlightenment.

If you’re anxious, it boils down to enjoying your comfort zone at an age when you shouldn’t be. I’m not advocating 996. But remind not to fool around, because fool around, will eventually mix yourself. Summarize technology in your spare time at work instead of watching live broadcasts, pesticides and masturbation.

When you are in charge of someone who is younger and more skilled than you, it may not be that he is very smart, but that he writes an extra Hello World when you are watching live broadcasts and pesticides.

The solution

• Read the classic source code to understand the ideas

Martial arts pay attention to teachers from famous, master guidance progress naturally fast. What could be more instructive than the classic technical framework, which is all about the craftsmanship of the masters?

Reading the source code helps us to learn classic technical ideas and code writing routines, in our future projects to build the wheel has ideological guidance value.

Reading the source code helps us to better understand the implementation and context of technology, to know yourself and know your opponent, in the online problem when solving problems can do accurate positioning, than others.

• Know what it is and why

Technology is a cumulative process, and you may have changed jobs over the years. Each company will definitely use different technology, excluding the SSM framework, it is certain that the new home will have technology that the previous company did not use.

When learning a new technology, we usually write “Hello World” by ourselves. However, we can only stay at the stage of knowing how to use it, but we must “know why” if we want to go far.

In my opinion, if a new technology is used in a company project, we should be familiar with the technology, including not only its API, but also the principle, source code and even the solution to production problems that may be encountered.

We try to avoid unnecessary relearning, because there are so many techniques to learn, when we touch it, we melt it into our own skill pool, and when we meet again in the future, we can take it out and use it, and we can make up for it.

For example, when new to the Spring framework, we should not only know how to configure it, xmL configuration, annotation configuration, etc., we should also understand his IOC, how to implement IOC, and the deeper spring bean life cycle. Once we understand the bean declaration cycle, we can use annotations and interfaces from various life cycles in our projects to implement our business requirements, such as @PostConstruct and @PreDestroy, as well as the role of the ApplicationContextAware interface.

• Record the blog

Blogging, I think, is what every technical person should do. In fact, blogging is not for others to worship themselves. The original purpose of blogging is to “learn from the past” and to deepen understanding.

Since ancient times has a proverb, or you will forget the “good”, again good memory to remember so many things, also have forgotten, we learn technology is a gradual process, maybe we will just use at first, then use the more our understanding of the technology and the deep, there is a “clearer to see the bright moon” feeling, to form their own understanding, This understanding may not be “unique” but it is our own.

What can we gain from blogging?

1. Blogging is your own thinking about technology. 2. Use it as a review note during the interview. 3. Writing well can increase your popularity in the industry. 4. It can be a plus in the interview.

• Save for a rainy day

We should never settle for what we already know, but embrace what we don’t know. During the interview, the interviewer may ask you to master the skills, but you can not find a job under the use of the skills you now know, prepare for a rainy day, learn some of the new technology on the market now, to your future career development can provide a wider path.

Maybe your company doesn’t have an architecture for microservices, but you can start by researching SpringCloud and Docker yourself. Maybe your project doesn’t use Elasticsearch but you can install it locally and use it. Opportunity always comes to those who are prepared.

• Be open to new opportunities

You never know what you’re capable of until you’re in a crisis. You’re not going to be an architect straight out of school, but you’ve done everything you can to prepare yourself to change roles when the time is right. I think any developer should be able to transition into an architect role after five years or so, because if you’ve been serious about the first few years, that’s when you can do it, and that’s around 30.

Personal public account: JaJian

Welcome long press the picture below to pay attention to the public number: JaJian!

We regularly provide you with the explanation and analysis of distributed, micro-services and other first-line Internet companies.