10 things that make programmers angry

Programmers are a very special group, because they have a long time to deal with the computer's character and temper is relatively similar. Of course, since it is a person, of course, there will be character, but also will have a temper. Now, let me take a look at 10 things that can annoy the program. On the one hand we can look at the commonality of programmers, on the other hand we can look at the shortcomings of programmers. In any case, I hope they will be a help to your daily work.

Tenth-bit program comment

program annotation is a good habit, when a programmer with a novice, always tell the novice, be sure to write a program annotation. So, of course, the Novice will follow the instructions of the veteran. However, they may have some misunderstanding of the program annotation, so we often see some of the following comments in the program:

Whenever you see a comment like this-just what the comment is, without commenting on why, I believe you will be angry, who wrote the program annotation ah? It's not snort to scold a meal. program annotation should be to tell others your intentions and ideas, rather than tell others the syntax of the program, this is for the readability and maintainability of the program, so the annotation for the annotation and annotation, clearly not in the comments, but in a provocation, of course, to offend others certainly.

Nineth Place Interrupted

Due process immersion in the programming algorithm of thinking, or the inspiration is in the process of writing a program, but it was interrupted by others, it is a very painful thing, if interrupted, it may be a sudden irritable. It is very impolite of people to interrupt others in this situation. The interrupted person is like a function call, when it returns, need to restore the breakpoint when the scene, of course, the person is not a computer, restore the scene is usually a very painful process, in extreme cases may need to start from scratch to find thoughts, and then 1.1 points back to the breakpoint.

Therefore, I see some programmers in need of quiet not disturbed time, either choose to go to a place where no one can find, or the top of their table hanging a banner to show the people-"I am executing the kernel program, can not be interrupted, please do not Disturb, thank you!" How much overhead it may be to interrupt a program that is immersed in a job. Naturally, there are also a few people who have been offended by the interruption.

Eighth-place Demand change

I don't think we need to say much about it. As long as it is a programmer, the face of changes in demand may always be very helpless. Once two times may also accept, but also can not withstand often change ah. It is said that there is a methodology in agile development that allows programmers to enjoy changes in demand, not knowing if they are true or false. However, today let you do a desk, tomorrow let you change the desk into a table, the day after next let you change the table into a double bed, the day after tomorrow let you change the bed into a small cabin, and then change the cabin into high-rise buildings. Well, people are going to get riled up. Those people can make any decision with a 30-minute meeting, but the next dozens of programmers need hundreds of hours of hard work. If it is me, maybe I also need to help solve the snort of the Beast grass mud/horse.

However, this also illustrates that programmers do not know how to communicate with users, and users do not know how to communicate with programmers, if a project does not have a middleman (such as: PM) in which to coordinate, then the whole project may be "'re same page", users and programmers will be annoyed by each other. If you want to cite a few users are annoyed, it is estimated that the programmer's kind of a tendon only from the technical implementation of thinking problems should also be ranked in the top 5.

The seventh manager doesn't know the technology.

Are there few examples of layman's leadership? The leader's words, whether right or wrong, are right, we have to do it, even if it's so stupid and so bad a decision, we have to do it. Programmers are not afraid of managers do not understand the technology, the most afraid is not the technology manager pretending to be very understanding of technology. The most exasperating is, when you stand for the leadership of the authority to choose, the leadership also treats you as a heterogeneous. Hey, think of such leaders don't say is curse, the impulse to hit all have.

In fact, the manager is just a team supporter, he should help the team, for the team to solve problems. Rather than dictating to the team. In fact, the management is really very simple, if you understand, to help do, if you do not understand, trust subordinates, let subordinates do. The most afraid is not understand the technology, but also do not trust the subordinate manager. Oh, this is really a programmer's pain.

Sixth user Documentation

The user documentation should not have been so scary. These documents record all the topics related to the software we have developed. Because we don't know what the user's computer operating base is, we need to assume that the user doesn't understand anything when we write this document. So, you need to write down one of the richest documents in the most clear and beautiful language. That is afraid of a copy paste operation, maybe we are divided into five or six steps to complete, even if a configuration IP address operation, we also want to start from the Start menu step-by-step description. For programmers, they use the software they develop almost every day in the development process, and in the end, they may get a little bit nauseous, but they have to write these documents from the simplest part, which makes them so annoying that it may be very bad for programmers to finish such documents. Therefore, for such user documentation, it should be done and maintained by a dedicated document person.

Fifth bit no document

As the previous article said, programmers do not like to write documents, and because the technical staff's ability to express and writing skills are generally not too good, so the document is bad. Take a look at the Open-source community's documentation and probably know it. However, our lovely programmers, on the other hand, are most angry because there is no documentation. Of course, let's say that the user's document, here we are talking about the development of documents, such as design documents, functional specifications, maintenance documents and so on. However, it is basically the same. Anyway, on the one hand, our programmers do not like to write documents, on the other hand, our program will be complained that there are no documents, too few documents, or documents can not understand. Oh. Originally in the complaining aspect also has the recursion. Agile development is said to reduce documentation in program development, and it is said that they can write code as if it were a document or an illustration, and don't know if it is true or false. However, I've heard too many programmers complaining about the lack of documentation, the poor documentation, and the blame for the programmers themselves.

Fourth-bit deployment environment

Although programmers develop software, we do not know what kind of environment our programs will be deployed or installed in, for example, different on the web, different on RAID, different BIOS, different operating system (WinXP and Win2003), no anti-virus software, and other programs are compatible, the system has rogue software or viruses and so on. Of course, as long as your software errors, whether it is your program problems, or environmental problems, anyway, it is your problem, you have to solve all. Therefore, programmers are not simply programming, many times, but also to be a good system administrator. Whenever the reason for the final confirmation of the problem is an environmental problem, it is likely that programmers will be angry.

Third problem report

"My software doesn't Work", "program Goes Wrong", and every time we hear a problem report like this, the programmer is always miserable, because such a problem report equals nothing, but programmers have to deal with it. There is no clear problem description, no description of how to reproduce the problem, in the sense that of course, it will appear a bit of the feeling of being questioned, even, in some cases also doped to look at, the tone of the reprimand, of course, programmers are basically very personality, are soft and hard not to eat, so, whenever there is such a tone report problem, They usually get their words back and, of course, there are some unpleasant things going on behind their backs. Therefore, we still need a customer service department to help our programmers and users to do a good job of communication.

The second programmer himself

To provoke hair programmers may or programmers themselves, programmers are "light", they are basically held only ALWU, always feel that they are the most cattle, in the programmer, they almost every day to quarrel, and a noisy agitatedly. Between them, they are always annoyed by themselves.

Different views on the technology. such as Linux and Win,vc++ and Vb,vi and Emacus,java and c++,php and Ruby, and so on. You have to fight about everything.

A veteran's contempt for a novice. There are always some programmers who look down on other programmers and talk with a kind of arrogance and reprimand. When a novice asks a question, the veteran is always in love.

Technically not to the other side to save face. Do not know why, programmers always do not give each other a face, whenever you hear someone mistakenly understand a technology, they always like to testify loudly in public, with others "mistakes" to show their "learned" and prove that others "ignorance."

Likes to despise. They like to despise, in fact, there is no one thing in the world is perfect, there are good there are bad, it is too easy to fault. Programmers especially like to despise others, no matter what things, they always like to see people short without looking at people long. The mantra that often hangs on their mouths is "too bad", "no" and so on.

Programmers, long-term and computer, write the code computer is always serious operation, Long developed the character of programmers supercilious, but do not know, this world many things can not be like a computer, as long as we enter the correct instructions it correctly run so simple. Programmers, when will become mature ...

Code for the first programmer

No matter how beautiful and classic you feel about your design and writing code, after a while, look back and you'll feel stupid. Of course, when you need to maintain the code of others, you must be in the side of the maintenance of the code to scold others. Do you remember how to talk about your design and how to be perfect with others? However, in two years, a fresh graduate from school in the process of maintaining your code can point to your code, so that your face completely sweeping. Oh. Of course, some people always feel that their design and code is the best, but this is a more static perspective of the problem. Programming This world change is always very fast, a lot of things, only when we have done, we are familiar with him, familiar with before we know what is a better way, this is gradual. So, when you become more and more familiar with things, and then look back at their previous design and code, the inevitable feel that they are superficial and stupid, of course, look at other people's design and code, may also start to curse.