How to [Post 51cto] from programmers to project managers]

How Program Member to project manager? This is a question for many programmers.
I. Height
Height determines the field of view .
First, you must have enough height,Cannot always start fromCodeFrom the project perspective, you need to look at the code from the project perspective.
Programmers complain that project managers often change their needs. Maybe your height is not enough. You are not thinking about the problem from the perspective of the Project Manager.
Ii. Responsibilities
attitude achievement height.
I often think: programmers are more important than technology.
Today, programmers are getting increasingly impetuous and lack a sense of responsibility. If you do not talk about a person's social responsibility for the moment, you should at least fulfill your responsibilities for this company when you work in a company. Only employees are responsible for the enterprise can they be responsible for the employees.
Many programmers like to talk about salary and are ready to change jobs at any time. I will immediately eliminate programmers ready to change jobs. Programmers should have a hard-working and honest traditional virtue. In this age of temptation, too many programmers cannot afford the temptation. They just jumped out of a company for two or three months, is a very common phenomenon.
Accepting any program requirements from the project manager is the root responsibility of the programmer. When you are a programmer, you must be able to work hard. Write your own program and complete all the details of the software.
Your best effort and hard work are two different things. In many procedures, you may have tried your best, but you are not careful enough and are not careful enough. It is a matter of attitude and responsibility.
Share a story: I used to evaluate the two programmers during the trial period. I asked them to write a database-targeted mini-Program for adding, deleting, querying, and modifying support documents.
Programmer A: Three days later, I went to see this small software. The function has been implemented and can be edited and imported into the database. However, I found that the function was not canceled. A document must be edited and imported to the database before other operations can be performed. One day later, I found that buttons such as "add", "modify", "cancel", "delete", "save", and "query" have different sizes and heights, the interface is messy. One day later, I found that after saving the document, you can still click the "cancel" button. After you click each function button, the other buttons are not blocked or hidden. After a day, I checked 10000 pieces of data in the database and found that all the software was loaded to the interface, no data is displayed or selected by page.
Programmer B: Three days later, I went to see this small software. The function has not been implemented yet. I am also asking about the detailed encoding technology issues in the database. The interface has been set up, the button style is unified, and various functional buttons are also controlled. One day, I went to see the software and asked my colleagues some code technical questions. One day later, I found that the function is ready and the problem of programmer A mentioned above does not exist.
So I hired programmer B decisively.
Many years of it experience tells me that skilled programmers are easy to gain superiority in their jobs. At the same time, these programmers gradually become arrogant and begin to focus less on code details. Regardless of the technical difficulty of our work, whether it is boring or not, we should always maintain a modest mind, take any task seriously, and complete all the details of the task, because -- it's our job.
Iii. mentality
Mentality determines everything.
I don't know when to start. It became synonymous with programmers. Programmers think that the pressure is high, the work is much more, and the result is less. If a group of people with a smart mind but little vision get together, they are easy to feel uneasy about the status quo. They always think that they should not be the current one. Start to scold enterprises, blame the party, blame the society, and start to ridicule themselves. Only one step at a time can we make great progress in our work by doing our job well, making positive progress, focusing on project managers and enterprises.
Some programmers asked me when he will become a project manager? I think you will never be a project manager.
If you can write code from the project perspective, if you can design a program from the user perspective, if you can think about the problem from the enterprise perspective, at this time: you are already a project manager.

This article is from zou Hui's blog