When every programmer struggles in the workplace, he will always develop some bad habits, which seem inconspicuous and insignificant. In fact, under the influence of these bad habits over time, they will not only affect work efficiency, but even be detrimental to personal growth. A stumbling block that hinders programmers' promotion and salary increase.
Today, I will summarize the 5 bad habits of programmers in the workplace for everyone , and see if you have been recruited.
1. Irregularly written code
Some people say that the second face of a programmer is the code. Although this is a bit exaggerated, it also proves how important the code specification is. When the code is written in chaos, reading such code is like being in a maze. You will gradually forget where you started, what you were looking for, and what this code accomplishes. If you need to fix problems or add features later, it will become very tricky.
Clear and standardized code is not only easy to read, but more importantly, it is easy to check errors and improve debugging efficiency. For individual programmers, standardized code is more conducive to helping them understand the development language, understanding model, and architecture, which is conducive to fast Raise the level of development.
2. Reluctance to learn and stagnation
Programmers who have no progress and growth are people who are unwilling to learn new technologies and refuse to learn. This industry is always changing. It may be that this technology is still popular on the Internet at one moment, and a newer technology will appear in the next moment. No one dares to say that he knows everything. If he wants to be at the forefront, he must learn more. When others are constantly working hard, but you are complacent about the existing technology and stop reading and learning, you will hardly escape the fate of falling behind.
Programming is a lifelong learning process . Whether you are a newcomer who has just entered the industry or a "veteran" in the workplace who has been struggling for many years, you should regard yourself as a student and learn with a humble and serious attitude. When you Every time you learn a skill, your own competitiveness will be stronger, and your capital against career crisis will be stronger.
3. Lack of teamwork ability
Junior programmers have a very easy problem, that is, when they encounter a problem, they will only die on their own. When the deadline leader asks, they will know that there is a problem that has not been solved. Not only did their own work not do a good job, but it also lowered the work of the entire team. efficiency. If you don't understand teamwork and don't discuss with the team, programming by yourself like a lone wolf may be applicable in the past, but it is a taboo now.
Communicate with team members in a timely manner , especially colleagues who are related to each other, raise problems in a timely manner when they discover problems , make adjustments and solve them, and reduce waste of time. This is not only responsible for their own work, but also for the team.
4. Refusal to accept constructive comments
When others put forward questions and constructive comments on the code they wrote, some programmers may feel offended, feel that others are denying their ability, and will directly reply out of self-protection instead of rational analysis There are pros and cons, and I will not accept other people's suggestions.
In fact, others may not give advice out of a nitpicking or suppressing mentality, but simply want to tell you a better way, or provide reasonable help. Constructive comments are an excellent resource for learning, but rather concrete solutions to problems you have now that others have suggested.
For the suggestions given by others, you can conduct a rational analysis first . If you are really just picky, or just pick and choose some irrelevant things, you can ignore them, but if you are really making reasonable suggestions, you can listen carefully. , making improvements, which is very beneficial for personal growth.
5. Unwillingness to review work
Many people think that review is a troublesome and meaningless thing. In fact, review is a link that can effectively analyze the shortcomings in the work and learn from work experience. Mistakes in the work are inevitable, but if you do it every time Falling down in the same place, making mistakes and not going back to the market, not learning from experience, making mistakes in the same place many times, this is a problem.
After the error occurs, it should be corrected in time. After the work is completed, you should remember to review the disk, first find out the reason for the error, why such an error occurred, and then find out the process to prevent the error from recurring according to the analysis. Next time Avoid the same mistakes at work.
Get rid of bad habits, maintain a humble and learning attitude at work , actively communicate with the team, listen carefully to other people's suggestions , and maintain these good habits in your own work, you can take a step towards a mature programmer.