Utopia Project Manager

As ProgramPersonnel, the project manager we want should be:
1. Initiative
It is impossible for you to expect colleagues at the same level to skip their own tasks and do not run them to help you solve the problem. At this time, the project manager plays a coordinating role. You should often ask the programmer about the situation and what difficulties do you need, do your best to use your rights to help programmers.
2. Timely bug fixes
The project manager should be able to grasp the priority of bugs, especially those unrelated to the business and programs. In case of exceptions and difficulties, he should work with the programmers to find a compromise to solve the problem as soon as possible.
3. Complete the task on time
He should have a more detailed understanding of the programmer's level, who is skilled in what direction, where he is interested, how he is at the current level, and what level he can raise, in the past, what was the cause of failure to complete the task on time? Generally, the task cannot be completed on time because of 1. The programmer level is not good. If this is the reason, the project manager does not have a good understanding of the programmer, the plan developed in this way cannot blame the programmer, 2. The programmer's understanding is incorrect because the project manager did not communicate well with the programmer and did not reach a consensus. Of course, this is the responsibility of the Project Manager. 3. If the project manager understands something wrong, there is nothing to say.
4. Innovation
There should be no innovation in the normal process, and there is no need for innovation. New methods and ideas should be precisely certified before being used in the work, blind innovation will only lead to project failure, and good ideas will not be certified. If there is a problem together, we cannot figure out whether it is a problem of innovation or the original problem, even if there is no problem, it cannot prove that it is the benefit of innovation.
5. Responsibility
A programmer does not need a sense of responsibility. The responsibility is defined by the system. As long as he completes the task as planned, he does not need to take such a large responsibility. The burden of responsibility should be borne by the Project Manager. Nice CodeIt is only available in the format specified by the Project Manager. The so-called "nice-looking" refers to clear naming rules, indentation of the same style, and comments of the same style. Programmers are not fellow programmers, how can I know the style and habits of others? If the project manager has no rules, there will be a wide variety of styles.
The format does not need to be advanced. It is only for everyone to be unified. A unified style can play a good role in discovering bugs and modifying programs, and can also save time.