The sea of bitterness is boundless, and there is no shore to look back.
01
Dangling, working in the Internet industry for five years, looking back silently, where do you look like a dim light?
When you first enter the workplace, most programmers will feel hard to learn technology, and later will go smoothly for promotion and salary increase. This idea is not wrong, but it is not comprehensive. After five years, will you continue to do technology and write code? This is the core issue.
When you first enter the workplace, you will feel that working hard overtime can continuously improve your ability. Companies that can learn technology can accept low salaries, but after five years, they will think that overtime is constantly squeezing their own room for growth. Low salary is life's sake. ceiling.
The key question I want to talk about here is that most of the cognitions and ideas that have just entered the workplace will no longer apply to the cognitions five years later.
After five years of work, the biggest pressure is to choose: workplace ceiling, technical ability ceiling, salary ceiling, 30-year-old ceiling.
How to face these problems is what most programmers are thinking about and entangled. The only point of reference for making a choice is to maximize the benefits, which can be understood as a better promotion and salary increase in the workplace, smoothly.
In five years, the biggest change is not work experience and ability accumulation, but mentality, clearly knowing that there is a huge gap between reality and ideals.
02
Looking back on my career for five years, the most recognized sentence is: learn to adapt to changes and accumulate abilities.
What has changed is the five-year time technical framework update iteration, development tools change, company environment teammate replacement, and even wanderings in different cities, thinking that the body and soul can be placed in one place, there is a classic saying: The only constant is the change itself.
What needs to be accumulated is: the ability to solve problems, the way of thinking, and the broadening of cognition.
This kind of hard-to-frank description belongs to the category of personal cognition. Different people have different opinions, so they can only think from the perspective of popularization.
Let’s talk about technology first. Most of the novices hope that their technical capabilities will continue to improve and strive to achieve the level of architects. However, in the current Internet environment, this idea is still difficult to implement. This is not a blow. It's not to lift the bar either.
You can observe the status quo. The technical team has 20-30 people, small 10-15 people, and it is rare to have an architect to manage the underlying framework.
There are many reasons for this problem. First of all, the cost of the architect is too high, and the environmental architecture does not need to be upgraded frequently. The ugly point may be that the framework is higher than the project life cycle.
Therefore, most of the business of most companies can be solved based on most of the existing mature open source frameworks. This also leads to the role of the architect usually being replaced by the project leader or the higher-level development is directly responsible. This is the reality.
This leads to the idea of choosing the technical framework: only choose the right one. That is to say, there are many talents in this area and many open source solutions to reduce the impact of technology on the company's business development.
Then why continue to learn and accumulate technical capabilities? Without this ability, the programmer position may not last for five years at all. It is necessary to use the in-depth accumulation of technology to continuously solve various problems in the work, and use the breadth of technology to enhance the cognitive boundary of achieving business needs. This is to place the body. Fundamental guarantee.
This is the reason for the sudden increase in the pressure of many programmers after five years. Another barrier to the management post is business thinking and cognition.
03
Should programmers study business carefully? There is really no need to entangle this question. As long as they are not purely technical companies, they need to face the business.
Regardless of technology, operations, products, and management, they are all working on business.
From the perspective of my career trajectory, the biggest change in the past five years is my ability to solve business problems. At the beginning of the workplace, I don’t know how to deal with many business scenarios, and will design business solutions a few years later.
This is the fundamental reason why most programmers can increase their salaries in the first five years of the workplace. Facing business scenarios, based on accumulated experience and existing open source tools, they can quickly give reasonable solutions and implementation processes.
Five years of work may not have a clear understanding of the underlying technical level of a newcomer, but the written program can avoid a lot of potholes, and the review of the business is also very detailed and comprehensive.
To solve the accumulation of business capabilities, the need for the breadth of technical horizons is even greater. For example, at the beginning of the workplace, there is no way to deal with massive data, but after a few years of work, seeing the technology stack of the data industry is really a problem of the vision of technology selection.
What is the standard for measuring technical capabilities? From the perspective of a consensus: the architecture and code design of the system can adapt to the continuous changes and various needs of the business.
Compared with technology, business changes are more rapid and frequent. The high salary of senior engineers or architects is that these roles can adapt to the iteration of the business on the one hand, and they are forward-looking in their work. They will consider code replication in the case of business changes. Using logic, this ability requires a certain degree of technical vision and precipitation of business thinking.
Therefore, in the workplace: the business can be described in order, the code can be written clearly, and the chances of getting opportunities are greater.
04
Looking at the two aspects of technology and business from a rational point of view, most people can go smoothly in the workplace, but the balance and choice of the two are different at different stages.
When thinking about how to choose, you can refer to the logic of the 28th principle, that is, in any group of things, the most important only accounts for a small part of it, about 20%, and the remaining 80%, although they are the majority, are secondary. Therefore it is also called the twenty-eight law.
Individuals really like this principle. Most people are not geniuses, so it is difficult to do several things half-heartedly at the same time. You should concentrate on doing one thing well in the same period of time.
However, the simple 28-principle model may not be suitable for most people in the early stage of the workplace, because there are a lot of things to learn in the early stage, how to survive in the workplace: professional ability, workplace relations, behave in the world, product design and so on.
Of course, these things do not have to be studied deliberately, but it is wiser to arrange the two, twenty-six principles or other combinations reasonably. First, you should focus on practicing professional skills, and secondly, you can choose one or two aspects according to your own interests to understand slowly. , Such as products, operations, operation and maintenance, data, etc. After all, it is difficult to say whether you will continue to write code after three to five years. It is always safe to leave yourself more opportunities.
In the early stage of the workplace, I basically think about problems from a technical perspective. How to quickly improve my coding ability is the primary goal of stability in the company. Therefore, most of the time I am doing basic coding and learning norms. At this time, it may be 90% of the time. The mind is focused on basic coding, and the other 10% will learn environment architecture.
At most one to two years, you will begin to be independently responsible for the development of module requirements, you need to design the entire code idea yourself, here the business will enter the field of vision, you must understand the business upstream and downstream relationship, learn to think about how to design the code structure, in order to change the situation The following code changes are less, this time may put 20% of the mind on the business side, 30% of the learning architecture.
This period of three to five years is the time when problem-solving ability improves the fastest, because programmers at this stage are basically developing core business links, such as trading, payment, settlement, smart business and other modules. Have a clearer grasp of the ability, otherwise it is to dig a hole for yourself, this stage requires a lot of hard work to think about the business flow.
The more the core business line, the easier it is for various problems to break out. If you don't bother to deal with various details in your daily work, the abnormally automatic messages and emails in the middle of the night will always make people haggard.
Therefore, studying technology hard is to improve yourself, and it is also important to cultivate your own business awareness. I personally think that the two components are equally divided, but a reasonable weighting needs to be made at the appropriate stage.
05
Based on technical ability and business thinking, learn to make choices and survive in the workplace, these are the biggest experience along the way in the first five years of the workplace.
Regardless of whether it is technology or business, these two concepts are still big propositions that are not easy to grasp, so learning to clarify the common modules in these two aspects is the key.
Regardless of technology or business, it is impossible to completely copy from one company to another, but one company’s technical framework and business solutions can be learned and brought to another company, such as the architecture, design, process, and Data management, thinking methods in the business field, product logic, analysis, etc., these are the core capabilities and are the requirements of most companies' talent recruitment, so these are the key accumulations in the work.
Human energy is limited, and facing the ceiling of thirty, various events will follow one after another. Learn to arrange time reasonably and continuously improve core competence in the workplace, so as to ensure one's competitiveness.
The workplace is like a sea of bitterness. Looking back, there may be no mooring on the shore, but it is not bad to have the ability to change boats or to have a small raft.
Read the label
[ Java Foundation ] [ Design Pattern ] [ Structure and Algorithm ] [ Linux System ] [ Database ]
[ Distributed architecture ] [ micro service ] [ big data components ] [ SpringBoot Advanced ] [ Spring & Boot foundation ]
[ Data Analysis ] [ Technical Map ] [ Workplace ]
