The pain of communication programmers

Stiff and silent

        The two term seems to have become a programmer's label, they reflect the image of the programmer in the commeunication performance. In the world of programmers, communication may include: communication with product manager needs to communicate with colleagues, and to share with colleagues and laymen, work and life stories.

        Some programmers to share anecdotes and on demand or technology performance or just a cheerful and be quite different, the guy suddenly became silent. Silence is sometimes do not want to say, especially in the communication demand, programmers thought: its pull so much, brother code are finished. It is not a small function. Silent, smiling without a word on the next, want to get to the end of the write code.

        This should be the programmers write code of the assets of the company, but the reality is that code is Linux or @antirez at the same time with the contribution of the assets and liabilities of the double attribute of the.Linus written in Redis which contains the code is an excellent asset, but most of us lack of communication needs, finally the write code are based on more liabilities than assets. Finally, is often out of the mix are to be returned, not their own is also others to also.

        The programmer might argue that communicating with people is not what we are capable of, not because we love to chat with other people to do software development in this line. This observation is very confusing, I once thought so early. When graduation to find work, such as foreign rizhongtian, went to the heart at that time the very cattle IBM interview. Most of the conversation during the interview I could not remember, is a problem still is very clear. The interview manager asked me: do you love more dealing with people, or dealing with the computer? Then I answer without hesitation love dealing with the computer. Love programming to write code, but also I'm not good at dealing with people.

        Then, I was eliminated. Later I realized, actually this kind of foreign name was hung with senior software engineer, the actual needs of the more technical background and understanding of the technical support, because they did not have at home a real R & D center. Now I think, even if you only only love to write code, and then the communication is still the bottleneck you cross the past. Write the code itself is a kind of communication, a written communication.

        Communication is always a problem, and written communication is equally difficult.

Argument and helplessness

      The programmer dispute are in place and peer communication, presumably a lot of people have had a technical scheme and peer debate. I myself had in the past years of work and colleagues had technical solution dispute, the lesson can be recommended to Technical Manager (main pipe): don't let two feel very cow programmer to design a technical scheme at the same time. Unfortunately, you have already done so and two different schemes, get so remember, don't make a mistake: let them take their own programs to PK. since the differences have produced, in order to avoid unnecessary controversy, how the solution?

persuade through reasoning

      First of all, to hold a degree, not the person, not the heart. Some technical points of disagreement between people is very strange, and this may be the technology of cleanliness, tastes and preferences. For example: the size of write, naming rules, braces to a hump or independent line, underline, Tab or space, they can produce differences. Once the outbreak is likely a Virgo mentality, hair get out of hand.

     If you because "some form of" how to do something or to do something and others have differences, so in many cases, you should first determine whether the bifurcation point is worth your hard maintenance. At this time, you need to determine whether a technology "reason" in what place, this "reason" is worth dying for you don't stick to the bottom line, with the "reason" can persuade each other?

    The "technology" of my understanding of technology includes: advanced, verifiable, adaptive (and team), timeliness, cost and benefits, and other inappropriate "principles": style, taste, unity, politics

     But sometimes, right does not mean you can fix the differences, to reach an agreement. Big woods, the unreasonable man is there, then the next step.

---