Ranking of problems that project managers tend to cause programmers to resist

　　It is a common phenomenon that project managers and programmers will have differences in the work process. If disagreements arise and are not handled properly, conflicts will arise. With resistance, there is no way to be so united when it comes to work. Therefore, how to deal with these issues is important. For some project managers, understanding some of the issues that are prone to conflict with programmers can also help them manage their teams better. When necessary, the project manager still needs to take the initiative to resolve the programmer's resistance. So, let's take a look at the ranking of problems that project managers tend to cause programmers to resist.

　　No. 10: Make unreasonable demands

　　Programmers are afraid of unreasonable demands made by project managers. It has to be said that in most cases, the project manager's thinking about product functions is correct. After all, this is the project manager's specialty. But, just like programmers make mistakes, product managers occasionally have their brains open. Making unreasonable demands makes programmers embarrassed. Refuse it, the project manager is definitely not happy, don't refuse, the product will be launched in the future, and I am embarrassed to say that this piece is made by me (covering my face).

　　No. 9: Blindly asking for plagiarism from competing products

　　"This functional competing product has it, so we have to have it too". This is a phrase that many programmers are afraid to hear. The project manager copy is cool, the programmer is suspicious of the meaning of life. Copy copy copy, why not let users use competing products directly?

　　No. 8: Know a little bit of technology, think "This question

　　has a saying that you are not afraid of hooligans, and you are most afraid of hooligans who can do martial arts. Don't be afraid that the project manager will not understand, just be afraid of the project. Managers understand technology. The project manager with half a bottle of water feels that he understands technology, is energetic, and can make decisions for you - "Isn't this problem solved by adding a field to the database? If you don't have time, I'll give it to you. Write a sql statement and you can execute it. "OMG, add fields and heads, I use distributed nosql db, how do you ask me to execute sql statements. Since you understand this, you can you up?

　　No. 7: Always interrupt you with meetings Work

　　Will, will, why are there always endless meetings! Writing code is high, and suddenly a meeting, the state plummets, and I don't want to write in an instant? If you want to make programmers have high-quality and high-efficiency output, It is still important to ensure that you are not disturbed. Project managers are strongly advised to reduce meeting time.

　　No. 6: Don't worry, I almost have to move a small bench to guard your work. The

　　programmer does not need a supervisor. If you believe him, please give him an independent space and let him work quietly and alone, which is more efficient. Of course, if you are a cute girl, then it is another matter.

　　No. 5: Anticlimactic, promises can’t be fulfilled.

　　Sometimes the project manager is hot-headed and takes the lead in promoting something with enthusiasm. The programmer will also think that the project has been done well, but gradually the project manager is tired. , Finally, the product function was launched, and the response was not good, and the project manager was unwilling to follow up. This happens once, twice, three times, and the programmers are no longer enthusiastic.

　　No. 4: Always ask programmers to work overtime It is normal for

　　projects to be busy and free, and it is okay to work overtime occasionally, but it is not good to work overtime all the time. After all, programmers are a high-risk occupation. With such high-intensity work, it is easy to raise programmers to death...

　　No. 3: Change requirements casually

　　If the project manager wants to kill programmers, frequently changing requirements is the fastest way. However, if you insist on doing this, you must also be careful about your own life safety...

　　2nd place: Use the boss as a shield in

　　everything function is required by the boss and cannot be cut. The functional boss said that it must be done, and the functional boss said that it will be done tomorrow... I really don't know if the boss will make the product or let you make the product. The boss is so powerful, why do you want your project manager?

　　No. 1: Deny your professionalism and work performance in front of everyone or the boss

　　The above 10 points, all developers and project managers have probably seen it. So, how to deal with these problems, you need to think about the problem. Small, I can't do it for you. After all, getting along with the problem still needs the parties to deal with it properly and effectively. Use more empathy, think more about the team's common goals and interests, and many things will be easier to handle.

　　This article is reproduced from Tuoyuan Youke: www.toyoke.com