I have been wanting to write this article for a long time, but I haven’t written it yet. I finally got it empty today and plan to sort it out.
The original time came from last year's "Project Manager Experience Summary" http://iamzhongyong.iteye.com/blog/1977551
In the past few years, I have done pure development in the project and also a project manager, so I have these conclusions. Some points are not very good, so let's take the right to reflect on yourself.
1. active, active
This is actually more important. If you say that the technical strength is not strong, and some things have not been used, these are actually not problems. As long as you take the initiative to learn, actively find problems, and follow up on problems, in fact, many technical problems are not problems. . This quality in the first place, I think it is very important.
2. Risks are thrown out in advance
There is definitely risk in doing a project, and without risk, there is no challenge. If you only rely on the project manager to control, firstly, the project manager does not have so much energy, and secondly, everyone's vision is limited. These two reasons may lead to incomplete consideration. At this time, every developer needs to be able to actively discover Risks, and come up with avoidance plans, if there is no avoidance plan, then put forward.
3. The new ideas are intended to be used in the project, and they have been verified by demo in advance.
Some classmates, including myself, will try some new things, such as new frameworks, new tools, etc. But there is a premise, don't think about trying new things when the project starts or is in progress, projects generally have time constraints. A colleague said that he wanted to use the XX framework in the project. At this time, he usually considers whether he has done it before. If he has done it, then feel free to use it. If he has not done it, it is best not to use it when the project comes. . Projects generally have a pre-research stage. At this time, if you have new ideas, you can try to make some examples. Why do you want to do this? Because new things have learning costs, this is second, some new things have pits in them, because there is no silver bullet in this world.
4. Take the initiative to undertake modules that no one is responsible for
The division of some modules may not be divided into specific people, because two modules may be connected. At this time, if time permits, it is recommended that developers take the initiative to undertake some modules that no one is responsible for. For example, the connection of two modules, the consideration of the security scheme of the overall page, the integration of unit testing, continuous integration, etc.
5. Help other colleagues after completing the part that you are responsible for
Is this the same as the previous one? no. No one is responsible for the one just now. This one belongs to other colleagues. The technical quality of the personnel inside the project may be uneven. Some things may be done by familiar people in a few hours, while others may take a day. At this time , if you are familiar with a module and another colleague is not, you can help.
6, the code is fully commented
Since most of the projects I'm involved in are business projects, one of the characteristics is complexity. At this time, it is necessary to have sufficient annotations, of course, it is only added when it is very necessary. As for what you can understand at a glance, there is no need to add it.
7. The code self-test is sufficient, and the modules that you are responsible for are completed with high quality
It must be mentioned that after the development students code is written, they need to be submitted to the test students for testing, and sometimes the test is divided into several rounds. At this time, the bug situation reflects the quality of the code, and the quality assurance, in addition to experience and code review, also needs to complete some self-testing things. In particular, the main process must have, and there are some boundary conditions that I feel. Some people say it's not a waste of time? In terms of time, this is to save time. After the self-test is sufficient, there will be fewer follow-up bugs, less rework, and fewer discussion issues, which saves a lot of time.
8. Smooth communication atmosphere
Isn't this talking about the team? No, it means that individuals, there are various roles in the project, communication is essential, why do you want to create a good communication atmosphere by yourself? Because you need to talk to others to discuss the problem, and others need to talk to you to discuss the problem. If there is a problem with the communication attitude and tone, a barrier will be built for each other, and this barrier will make the communication between everyone not very smooth, which may eventually lead to a The problem is not understood by everyone.
9. Assist the project manager when necessary
The project manager is sometimes too busy. If your time and energy allow, then help the project manager.
10. Responsibility
Putting this at the end does not mean that the ranking is at the end. I think this is also very important. Just imagine the code written by an irresponsible person. Can others trust it.
In general, these are on the line. Project management is a long-term topic, and it will continue in the future. It can be regarded as a staged understanding of myself.