Warning do not mix with project managers without business design experience

Warning do not mix with project managers without business design experience or development experience

This article is not only for programmers, but also for enterprises to understand and not to harm and spoil programmers. When the management layer understands and understands the hard work of programmers, this is a common phenomenon, not a personal phenomenon. This is an objective fact, not an emotional blow.

 

It is normal that the project manager does not write the code, and does not write the code too much. Maybe the project manager will not write the code after a long time. However, some young project managers are programmers who cannot write the code well and direct the code to the project manager. You should be careful when writing the code, the trouble is that there is no development experience or business design experience at all. What's even worse is that he has no business design capability.

The high salary of the project manager is because the project manager requires Nb better than the programmer, that is, Nb can only build one small module for customer communication and large-scale system design planning, the Project Manager can estimate the complexity of man-month, and the project manager who does not know the development and design will only count on several pages.

The tragedy is far more than that, and the design capability is poor. When the customer raises the demand, it cannot be converted into a specific business design. Even if there is a problem with the demand, it cannot be converted, after that, we will try it out. Simple things will be difficult to do, let alone complicated things. The Project Manager can not do a specific design, but the premise is that the demand is clear, but unfortunately his document looks at his needs cannot be designed at all, you can guess N types of design, he also thought about what he could design.

Like my current project manager, the first few projects were not designed by him. They were all just done by others who understood the demand design. At least if there was a big framework, the errors would not be enough, this is a very simple project, that is, he understands the needs and design by himself. We cannot design the requirements he understands, his design is just in conflict with the requirement document he wrote. Well, a few items are put into a table, check whether review is the same thing (check and review should have done almost the same thing, that is, a table, but it is different in his design and no longer a table, but it should be placed in a list (the union of the two tables), and the fields are almost the same ...), Obviously, what is not in a data table needs to be pushed to a list, and the design becomes more and more complex. He always says, "Oh, it's very simple." "Make it simple first ", every time he said this, it was a tragedy, and the results were all overturned or failed. It was very troublesome to add things, so he could advise me not to listen. Simple things were complicated, and the design capability was not as good as that of college graduates. Executives who indulge in such problems are also very problematic. To put it simply, you only need to talk about the demand. Unfortunately, the demand is incomplete and cannot be designed. You have to design it on your own. His design can also conflict with the requirements and documents.

 

Theoretical things will read books and blow Nb. He prefers a book called man-month myth. Unfortunately, he is incapable of calculating the workload and considering risks in advance, it's really a mythical man-month. He also said that the most important thing to do a project is man-month. Well, it's a myth.

My project manager didn't see this bad thing either, but the document was sharp. Specifically, it was worse than my project manager.

There is another problem in many companies, that is, they like to invite executives from the outside. In fact, many executives are arrogant when they become executives. If they are invited outside, they have to spend time teaching them, after teaching him, he continued to brag and forced other companies to mix up, or he went on to brag and forced him to change places, therefore, it is best for a company to select a manager to promote from its own employees. It is not like some people who mix executives and do nothing to harm their subordinates.

 

 

---

Someone has to ask, but I want to raise a solution to keep up with the first question. What about the solution? I am too lazy to say that I am capable of reading and promoting from programmers with communication skills and development experience, rather than just looking for a programmer, don't let people think that you can be a project manager. Write the code first.

To be honest, there are a lot of project managers around me who can write code and have technical skills. How come? It is a real programmer. Do not give shortcuts.

----

Someone else has to say that you will spray it. Don't say it's sour if you don't get the grapes.

The project manager is just a profession. If it is not good, you should scold me. Why? The project manager is boring and has no time to play with technology. I despise the IQ of executives. Are you still jealous of the Red Cross? Are you jealous of the Red Cross? if others are greedy of you, then you are sour, right.

---

Pay attention to quality, not regional guns