When many programmers reach maturity, they will be stuck. Technically, I have been familiar with it, and I have been working on a step-by-step basis. Although I feel a little unwilling in my mind, they are very helpless in what they want to do. I think that when programmers reach the maturity stage, if they want to develop towards the excellent stage, they will certainly encounter this bottleneck. Passing Through this bottleneck will go into another broad prospect, if you do not wear it, you will stay in the same position.
1. Technical bottleneck
The technical bottleneck is obvious, mainly manifested in the lack of enthusiasm for learning, lack of research on technology, lack of understanding on the development of new technologies and other three main aspects. The main reasons are: first, mature programmer programming technology can already meet the requirements of software development. Many people think that as long as it can be compiled, it depends on the interest, and the viewing time is allowed. Second, since mature programmers undertake more work than general programmers, such as software design and project management, such as dealing with users and leaders, they cannot focus much time on programming. Third, because software development tasks are usually relatively tight, it is necessary to work overtime to complete, so there is no time to do further technical in-depth. Fourth, many programmers are in a spontaneous state of development. Their own growth depends entirely on their work content. The strength and complexity of work content determine their technical level. Therefore, he does not know the direction of his own technological development or the technical gap.
Therefore, mature programmers should have a higher level of consciousness and never stick to their own secrets. First, you must have an objective analysis on your technology to see where your long term is and where the weak item is. You must find a way to overcome your weaknesses and never stay there. Your progress will inevitably be affected in the future. For example, many weaknesses include object-oriented design methods, human-machine interface interaction, processing of large data volumes, and processing efficiency. If there are any problems in these areas, we should try our best to solve them. Second, we should pay attention to the deep understanding of basic programming skills. In many cases, programmers only come to the principle, knowing why, and making up the missing part of the foundation, to lay the foundation for a higher level of technology, such as operating systems, network knowledge, programming language, database, system architecture, software engineering, and other basic knowledge, we need to review it, master useful knowledge, and learn to link all kinds of basic knowledge to deepen your understanding of basic knowledge. Third, it is necessary to gradually turn the programming technology from the function implementation aspect to the research of parametric design, software architecture and other advanced stages, and make achievements in sharing, General, and standardization.
2. Work bottleneck
Programmers also have upward bottlenecks at work. In general, many programmers work relatively stably at this stage: the leaders have a relatively good understanding and trust in themselves, and their colleagues also agree on their work ability and technical level, software Users are relatively satisfied with their own services. Therefore, while working day after day is full of work satisfaction, there is no new idea, and the feeling of fatigue arises. In the past, that passion was rarely released. Therefore, Programmers sometimes think about where they want to make breakthroughs in their work and how they can take them to the next level.
The current situation of programmers at work is still caused by the arrangement of software companies or department superiors. Although they have paid a lot in their specific work, they have a lot of autonomy in programming, but in general, programmers are only the executors in the business process and are passive roles. Therefore, to change the current situation of a programmer at work, the programmer must be proactive and plan his own development direction as much as possible, actively reflect your thoughts and plans to win the understanding and support of your superiors, and put your time, energy, and focus on your own concerns when your work conditions permit. For example, programmers feel that they have already met their work requirements in programming, but they have the ability to deal with customers and the accumulation of market resources is poor. He can propose to his superiors that he wants to do pre-sales work. If the leaders agree, he can improve his abilities in this position. If your position is not adjusted, you can deal with the customer as much as possible based on your work scope to understand the customer's needs, so as to lay a good foundation for your own projects, at the same time, by dealing with customers and making friends with customers, we can accumulate market resources for ourselves. In fact, there can be many improvements at the work level.
3. Income bottlenecks
In the end, the biggest bottleneck for programmers lies in the income bottleneck. After years of hard work, the income has also improved, and some have even reached the average social income level. However, in the face of China's daily life, it takes decades to buy a suite (even if the mortgage still has to pay the principal and interest every month ), moreover, it is difficult for the job to remain stable for decades (unless it is a civil servant ). Therefore, the income of the vast majority of programmers is difficult to meet the requirements of the programmer's yearning for life, especially the requirements for a moderate life and a stable life. Of course, there are always exceptions. A very small number of programmers earn a very high income and their lives are very moist. In general, what we pay and what we get are out of proportion. This is a sorrow of society. Back to the specific circumstances of a programmer, the programmer's income is generally relatively stable, sometimes once a year, or several years, depending on the situation of the company and the department of the unit. Like employees in other professions, programmers rarely have their own right to speak in terms of wage income.
After the programmers experienced the ups and downs of the growth process, they reached the maturity stage, and their income should be much higher than in the past. However, the contrast between the programmer's expectation and actual income is the biggest headache in the programmer's heart. Therefore, increasing income or substantially increasing income is a bottleneck that programmers cannot break through.
In the face of revenue bottlenecks, programmers should adjust their mentality. It is absolutely useless to rely solely on complaints. To solve this problem, programmers can consider the following aspects. First, programmers can tap the potential of revenue growth in their own company departments. They can take the initiative to propose adjustments to high-income positions and participate in high-reward project development, all jobs that can increase revenue can be considered. Second, on this basis, if the programmer feels that his income still cannot meet his expectations, he may consider leaving the company or department to raise his income by applying for a high-paying job, of course, we should be cautious in this choice. We should consider multiple factors. In many cases, income is not the only factor. The gap between future income and existing income is negligible. Third, programmers can engage in some secondary occupations with the conditions and energy permits. Due to the professional characteristics of programmers, programmers can complete a programming task independently, programmers can also work with others to complete programming tasks. By engaging in the second profession, programmers can enhance market awareness and learn more about the value of software than their own companies and departments, get to know more software peers, learn more programming technologies, and get the appropriate labor rewards. More importantly, you may encounter development opportunities during this period.
Programmers who meet the current situation cannot meet these bottlenecks. They will be satisfied in their own world, and they will continue their work and seek a peaceful life. Mature programmers who do not meet the current situation and those who pursue excellence are confused by the pursuit and strive for breakthroughs due to bottlenecks. As long as programmers are unwilling to the status quo, as long as they decide that everything depends on themselves, as long as they are prepared to pay more energy than they used to, as long as they are prepared to overcome more difficulties than they used to, as long as they want to seek new changes, it will eventually break into a butterfly. Under the gorgeous sky, the Colorful butterfly flying freely is exactly what they will look like in the future.
Bottlenecks from maturity to excellence
