The need for programmers to reflect on themselves

Most programmers know that most programming problems end up looking at their personalities. When we encounter strange problems, we are always used to doubt the system, suspect the network, suspect the compiler, suspect the hardware ... is not willing to doubt their own character. After a few sleepless nights, eventually found that their own code is a problem. And only a very small number of cases, is the problem of the system.

Similarly, some programmers in the career development problems, is always used to doubt the company is not good, doubt the strategic issues, suspected process system unreasonable, suspicion of bosses and colleagues ... is not willing to doubt their character.

In the large and small it enterprises, can always see some technology is not the best programmers to make great events, but also always see some technical cattle are buried and can not show the talent of the phenomenon. I think, in addition to the opportunity, there is a very important factor, that is: the Programmer's character!

Of course, this "character" is still a statement of ridicule, not a moral issue. In fact, character refers to the soft power of programmers. If the programmer's programming skills are called hard power, then everything beyond programming skills can be called soft power. No doubt, programming skills is a good programmer must have the hard power, the programmer's career development plays the most direct role, but the programmer's soft power can not be ignored.

How to cultivate your own character? I'd like to talk about some of my own experiences and lessons.

Programmer Light

In the process of dealing with programmers for a long time, I found that most programmers, like me, prefer to be self-centered, especially young programmers. Perhaps my observations may not be entirely correct, but from the behavior of many programmers, I can really feel the impetuous mentality.

Like self-centered people, tend to be self-righteous, and according to their own ideas and ideas to act, not too willing to listen to other people's ideas and opinions. At the same time, such people, a relatively introverted personality, like to immerse themselves in the illusion of narcissism and conceit of the space, other people's ideas are not seen. When two very self-programmers meet, they do not listen to each other and learn from each other's strengths, but prefer to find each other's shortcomings, thus showing off their advantages. This is the so-called "programmer light" phenomenon!

I do not know whether programmers have a light mentality, anyway, I often look down on other programmers, and even look down on those venerable old-timers. There are few programmers I can appreciate. My colleagues wrote the code in my Eyes is pediatrics, or simply rubbish. I know a lot of programmers who come over, who have been very self, but have now put down, and thus unrestrained programming. They are now playing an important role in some of the company's teams, but according to them, the "light programmer" phenomenon is common in IT companies.

Today's software development, most of the need for teamwork to complete. Team warfare requires a team of each programmer to trust and respect each other, the dispersed forces together to form a joint effort to conquer one after another project engineering. If a team of programmers in the light of the serious phenomenon, members of the team will be from the mutual debate into mutual accusations, gradually lose the mutual trust and respect between members, internal friction increasingly serious. In the end, the team's power is torn apart, everyone is not in the same direction, and the whole team becomes defenseless.

I think, for the professional development of programmers, the first hurdle is to overcome the "programmer light" mentality. Only by correcting this character can we liberate our thoughts from the narrow and closed self space, and then embark on a broad career development path. So is it hard to overcome the light mentality of programmers? It's easy!

The most difficult opponent in the world is "ego", and the heaviest baggage in the world is "ego". Because the ego, people will be narcissistic, the heart will be selfish, the line will be conceited, proud will deceive, defeat will inferiority. Programmers light This one of the biggest character, is because too ego. If you dare to say "my character is no problem", then you have to let go of yourself. Put down the ego, character also put down. In this way, why don't we put down the heavy baggage and let the mind relax and free?

Communication

Most programmers are more subtle. We prefer simple technical work to complex interpersonal relationships. Therefore, when communicating with others, programmers will show two aspects of the adaptation: one is not good at listening, and second, is not good at expression. Actually, I used to do the same. I like to be silent while listening to other people's speeches, but I always think of my own ideas. When it was my turn to speak, I could not express my thoughts effectively, and the words were difficult to understand. Sometimes, they like to interrupt others to speak, to impose their views, and whether or not to understand the meaning of the other side, the big accusation, or even a rude remark.

Communication barriers are another common character of most programmers. And in the team collaboration is unavoidable to communicate with each other, if a programmer in communication obstacles, it is difficult to integrate into the team development work. Therefore, programmers should strive to improve their communication skills, cultivate the character of communication. Of course, improving our communication skills does not require us to be eloquent as a debating speaker, as long as we can effectively listen and express effectively.

In fact, it is easier to listen effectively, especially when the other party's expressive ability is very strong, we only need to calm down to listen carefully. Even if it is not easy to understand other people's words, ask more and ask each other to speak again. Anyway, we must first understand the meaning of others before expressing their opinions. Perhaps in your opinion other people's idea is wrong, may as well first let the person say that finishes. Maybe you'll find out you're wrong, even if you're right, and you'll probably get the wrong idea. Understanding begins with listening, and listening attentively embodies respect for people. Put yourself in your shoes, and if you are speaking, do you want people to listen to you and understand your thoughts? So why can't we just listen when someone else is speaking?

However, the purpose of listening is to understand other people's thoughts. Some people are silent, seemingly listening to other people's speeches, actually thinking of other things, while others pretend to be pretending to be misunderstood and to understand. For effective communication, these phenomena are not beneficial, but will bring more disadvantages. Problems can not be solved, hidden dangers buried deeper. So listen carefully, try to understand the problem from the narrator's thoughts, and really understand what others think. Understand, do not understand do not understand, do not pretend to know. Whether you are a rookie or Daniel, ask more, no one will despise you!

In contrast, it is difficult to express effectively. Many programmers have this feeling, let me write code easy, let me say it is difficult. Unfortunately, the code is addressed to the machine, communication and communication is facing people. Therefore, it is also very important to improve the ability of language expression, unless you are not going to deal with people.

In fact, there are some simple principles that can be used for reference in language expression. First, remember, in any case, to grasp the logical clues to the speech, and secondly, to start with the background, to establish the context of communication, to speak specific details, and then to insert a brief explanation of the key words in the explanation. I believe this explanation is understandable to many people. It's like programming, you have to have a complete logical line, a context, a variable definition, and so on.