Be a different programmer

From now on, don’t be that programmer who only immerses yourself in writing code, and look at what others do.

First: Ability is fundamental Engineer

A: Silly, customer XXX’s network is down. I have a lot of things on hand right now that I can't handle. Could you please help solve this customer's problem?

Xiao Sha: Um, what is the reason why the customer is disconnected? How can I check it?

Engineer A: XXX

PS: I know the reason If the network is disconnected, do you still need to troubleshoot? The network is down, don’t you know how to troubleshoot? Don’t you know how to understand the network environment and topology from the customer first? Don’t you know how to ping the gateway? Don’t you know how to capture packets on the wireshark port?

If the team wants to hire someone, who would you hire? Everyone hopes that the members of their team can be independent! Everyone wants to work with experts, especially programmers! Therefore, everything depends on their own abilities. That’s the fundamental! If you are a great person, even if you are full of quirks, everyone will still think you are cute! Ability is the core competitiveness of a programmer!

Second: Be a proactive programmer

Xiao Sha: Manager, the customer said that they want to add a historical data curve query function. How do you think it should be done?

Product Manager: XXX

The correct approach It should be: Manager, the customer said that they want to add a historical data curve query function. I thought about it carefully and there are probably two sets of implementation plans. Plan one: XXX, plan two: YYY. Which of these two options do you think is better, or do you have any other options?

Don’t think that you are a programmer, you only need to be responsible for code implementation, and design has nothing to do with you! No one wants to have such a subordinate. Being your boss is really tiring!

Third: Emotional intelligence is very important

Manager: Why does this interface not display anything and report an error again?

Front-end programmer : It must be that some program in their backend has corrupted the configuration file, causing an error in the interface reading the configuration.

It’s not a big deal if the program has bugs. Don’t always blame others for the problem. When you say this, the brothers in the backend development will take offense and offend a lot of people. And the manager’s impression of you won’t be much better, right?

Fourth: Have a sense of ownership

Case 1:

When you see a pile of pulp code, there are usually two reactions.

Reaction 1: Damn, this code works too!

Reaction 2: Wait for some weekend, I will refactor the code of this functional module. The code is too ugly and difficult to maintain. !

Case 2:

When customers reported product bugs, because the person responsible for this functional module had resigned, no one took over for the time being. In the absence of a clear stipulation on who is responsible, who should fix this bug? Usually we programmers behave in two ways.

Performance 1: It’s none of my business.

Performance 2: Send me that case!

Well, the implication of this article is, don’t be afraid of suffering losses, treat the company’s affairs as your own, and don’t take a penny. , do things for a penny” mentality. If you regard your work as a career, it is usually easy to do this, and naturally no one can replace you.

Based on the above analysis, it is useless to just work hard. If you want to be invincible in today's society and not be easily eliminated, you must have a skill, enhance your core competitiveness, and improve your skills. The gold content becomes the irreplaceable one. Naturally, you will be the one who laughs last.