Experience: Top 10 Career Survival Tips for Programmers_html/css_WEB-ITnose

Abstract: With agile development, development As operations and distributed version control systems become more and more popular, the focus of development gradually shifts from individual capabilities to group cooperation

Original English text: Ten career tips every egocentric Programmers should hear

Translated author:? Jiang Lili

If you want to stand out among many programmers, the following phenomenon is worth pondering : As agile development, development operations, and distributed version control systems become more and more popular, the focus of development gradually shifts from individual abilities to group cooperation.

In most cases, teams, departments and individuals will solve the problem on their own, and the team leader will The final project turned out to be very limited in what it could do.

The central idea and theme of all the techniques in this article is "Don't be mediocre, live for yourself". Well, persevere and learn the following ten professional skills. They will be your ship to ride the wind and waves and take you to the other side of success.

1. You are the best

Believe that you are the best programmer and be full of confidence. As time goes by, you will have more and more admirers. Don't worry about making a fool of yourself, IT is so complex that you can always pass the ball to someone else.

2. Your code represents you

If a colleague finds a bug in his code, first Admit your mistakes? Even if it's just a few extra clicks on the keyboard. Ask them afterwards if they had any problem with you personally.

　3. Treat programming skills as top secrets

The more you know about this kind of programming skills, Then your status will be higher among your peers. Use your own magic tricks frequently, but remember not to overwhelm your skills. Another point: don't steal other people's tricks, and don't lower yourself.

4. Rambo mentality

The kind of developers who can write new software components overnight alone Is "Rambo" a lone hero? Don’t bother with code review systems and pair programming. Those who need to do this are newbies, and they will only ruin your reputation.

5. Knowledge is power

Let those who are not as good as you know your advantages. To remind them, it would be best to have a mentor.

6. The fast fish eats the slow fish

If you still think like the tortoise in "The Tortoise and the Hare" If you win the race by going slow and sustained, you lose. The sooner you can complete the component development of new software, the greater the probability of success. Don't waste time on things like modularity, flexibility and maintainability - if you have to consider these issues because your needs are different, that's not your fault.

7. Authoritativeness has nothing to do with programming

Authority comes from your company status and has nothing to do with your programming ability. When you finally change from an ordinary developer to a team leader or project manager, your first consideration is no longer whether you can keep up with everyone's programming speed.

8. Don’t accept failure

Failure is never an option for us. If your idea is refuted in the group meeting, design a perfect, top-level sabotage and sabotage campaign, and if something goes wrong, you can triumphantly declare: "I told you so!"

9. Enhance relationships with people in the same department

Don’t always go to other department offices, otherwise your Colleagues will label you a "traitor." In any case, developers in other departments can provide very limited help compared to the elite people in their own department.

10. Treat bugs as opportunities

Some critics who especially like to comment on other people’s mistakes will see them in the code. The bug is elated. Try to use clever words such as "Typical error, variable names are confused again!"

Finally, I would like to warn everyone not to work hard and dedicate yourself to the team, but in the end it will be thankless. If someone uses Gerald M. Weinberg's "10 Commandments of Selfless Programming" to refute, then I can tell you that this thing was written in 1971 and has been completely out for a long time.

The information on this site is selected by HTML5 China editors from other media HTML5 Relevant information is reproduced for the reference of netizens. Submit to: news@html5cn.org