In the eyes of programmers, users use the software they developed in this way.

I once said that programmers are not ordinary people, but people with certain super abilities. But the problem is that programmers often do not realize their own special functions. In their eyes, they will think that they are very ordinary, just like ordinary people, So what programmers can do, other people-such as their customers/software users-should also be easy to do. But in fact, most people-most people (including software development company customers/users who buy software) -- people who know little about computers, computers, and software ). A software operation that is very obvious to programmers. A variety of strange things may occur when users operate it. This makes programmers very painful.

I remember one time, a customer called me and said that he could not find the big E on his computer desktop. I didn't understand it. What big E could not find? The customer explained that the long e-like icon could not be found. Me. Finally, I realized that the Internet Explorer icon on the desktop is missing.

Another time, a customer asked me to add a search function on the page. I asked him why the search function is available in the system, he said that he didn't want the search. He wanted to search for a keyword on this page. After further communication, I understand that he wants the shortcut key Ctrl + F on the browser.

Because of these characteristics of users, Programmers think that the perfect program is in the hands of the customer, but it becomes extremely difficult to use the software, complaints such as the country, the street is like a burst of sound. After the analysis, the root cause was that programmers overestimated the user's ability to control the software and underestimated their ability to create the software, as a result, they see that these customers use the software they developed, it is such a ridiculous behavior, such:

In the eyes of programmers, users use the software they developed in this way.

If a grumpy programmer encounters such a situation, he will inevitably complain to the customer. Moreover, the programmer's temper is generally not very good. Therefore, when communicating with the customer, generally, project managers are working together to avoid intensifying the situation.

Users bring a lot of trouble to programmers, but in fact all the honors of programmers come from the customers, because only when the customers are satisfied, the programmers will have a sense of accomplishment. For example, the expressions shown by the following customers when using a new software are enough to make a programmer in Beijing's afternoon smile:

What a user looks like when using a new software

Programmers have bad temper, but they are thinking about their work without any personal complaints. When there are urgent tasks for developing software, they all work hard and work overtime. When a major bug occurs in the released software, they will be deeply blamed, they will work out urgent bugs overnight. If they cannot satisfy users in the first time, they will not think, eat, or sleep. Even if there are no complete remedial measures within a short period of time, they will come up with some tricks, but they are also an effective solution that allows users to temporarily tide over the difficulties. For example, the following is an emergency repair patch:

Urgent patch repair

Users should be considerate of programmers. The programmer's life is in a very contradictory state. Programming is not like other industries, such as bricklayer bricks, build a layer of bricks, the wall will be once higher. But programming is different. Sometimes a programmer writes the code for a day, and the development progress may not be significant, and sometimes it may even go backwards. Software programming is a virtual and real world. Sometimes you cannot figure out why a piece of code is easy to use, and sometimes you are surprised that software composed of that code can also run, as shown in the following figure:

Ghosts in the software

Finally, let's talk about some precautions for dealing with programmers. Programmers are especially sensitive to causal relationships because they deal with programming logic all day long. If the causal relationship of your discourse is not clear, it will make them confused. If the causal relationship of your discourse is incomplete, it will make them do wrong. If you haveif, It is best to use laterthenOr useelseGive a choice and clarify the subject. If it is not clear, an accident will occur:

The programmer understands the words on this card in this way.

If you are a programmer, you will understand what I said.