How can programmers resolve communication conflicts and avoid tearing each other apart?

If programmers want to solve communication conflicts, they must have their own real strength and show their real talents, so as to avoid tearing each other apart and protect their real interests.

And this kind of strength is completely based on the experience accumulated in the work, do some things must make yourself ten out of ten, do not verbally promise some work things, so that it is very unfavorable to yourself, must be documented so that you can avoid a lot of unnecessary trouble.

The work of a programmer is very tedious every day, and the work faced by yourself every day is boring and boring, and this boredom also needs to exercise your willpower, so that you can find real fun in your work.

In this kind of work, you must master some real skills when communicating with colleagues, and such skills are completely based on the contacts you usually accumulate to establish such a relationship, so as to have a good communication environment with colleagues.

It is especially important for programmers to have a good network in their work, so that they will not have real quarrels because of some, and also let themselves establish a good image, such an image is the authority to speak that they have won by working hard at work, but the promises made when doing things must be fulfilled in order to have such a foundation.

With such a foundation, programmers can avoid tearing each other apart, reduce their interests to the minimum, and have a communication environment, that is, the contacts they have established.

Programmers and product managers are at odds, because product managers often ask for changes in requirements, and programmers are generally typical science and engineering men who are not good at communicating. Last year, there was a meme that was popular in the Internet world where a product manager asked a programmer to tweak a page, and then the programmer pulled out a knife. This is a pain experienced by programmers, and in the face of the demand side, how to adjust and modify, the most important thing is to keep evidence in everything we do.

At work, it is inevitable that the demand side is not too satisfied with what is being done or that some things need to be adjusted. At this time, in order to solve unnecessary troubles, it is absolutely impossible to change it verbally. Because if this is the case, if the final result is problematic, the programmer must have an unshirkable responsibility.

So in order to avoid liability problems later, when we modify any page or other thing, we need to have documentation, and preferably by email.

If we have an email in hand, at least the final result is satisfactory to the demander, as long as we do what the demander asks, even if the final result is not satisfied, it is a matter of formulating requirements, and we can re-optimize the requirements, so as to avoid unnecessary trouble.

Under normal circumstances, the program ape can maintain a good daily relationship with the product, eat lunch together, participate in team building together, etc., the daily communication is smooth, and it is relatively easy to communicate with the product.

In the battle like the earth-shattering program ape beating the product manager, it is said that the product manager put forward a request to achieve the client's color adaptation to the user's mobile phone case. If the programmer and the product manager get along better, they can sit down and communicate.

Brother, you're not doing this trick."

What's not going to be funny? ”

I'll tell you, technically, this and that."

Oh, I see, or you're professional, listen to you, then this feature doesn't matter."

Communication can solve the problem, such a result, everyone is happy.