"Self-pressure" in software development"

In the software field, there are many cases of development failure because the idea of software engineering is not used, today, software engineering ideas and various theories that encourage efficient and successful software development are emerging. Project Managers, system architects, and staff on all fronts have attached great importance to them, at the same time, more programmers are thinking, and more excellent management talents are practicing! However, have we noticed the following problems: Project Manager, Development technical backbone, andProgramWhen did they start programming? Did they develop software independently or together with their partners before entering the development team ?......

The answer is clearly that anyone starts from programming by themselves. They have developed software more or less independently. But do they have any idea to implement the idea of software when developing software independently? I think it's hard to do it! Without pressure, it is difficult to be strict with yourself. For me, I recently developed a software sales company website (JSP + Struts) with my friends because it was our own project, there is no pressure at all, it may also be poor self-discipline ability, and the development progress is very slow. Although the heart is full of expectation, it is not easy at all. We have a similar mentality of value, this forms a strange mentality of "slower than", resulting in a longer and longer project development time. At first, I suggested writing the progress plan, but the old man said that the writing was also a white write, and certainly could not be completed on time. At that time, I thought it would also be acquiesced. Now, in retrospect, that idea is extremely wrong! Of course, not all programmers, like us, have seen the technology published by many outstanding programmers on csdn.ArticleThey all wrote detailed schedules and time limits, and the blue sky moderators also wrote detailed schedules, and summarized them at the right time after the work was completed to summarize the reasons for project delays, this is a good example for us to learn!

After all, most people do not do well! So I think it is necessary to talk about it here. In personal or small group software development, we should try to do the following:

1. Develop detailed progress plans (even if they cannot be completed on time );

2. Make sure that the idea of software engineering is always taken into account in the development project and should be developed according to the process as much as possible;

3. Strive to improve your programming capability and optimize the program structure (to finish the project on time );

4. If you are fighting for multiple people, keep yourself in a hurry and never fall into a "slower" cycle;

5. After completing the project, make a careful summary and accumulate experience for the next development.

I think we started to develop good software development habits before we started our job. After we really set foot on our job, we will soon adapt to the development of the group and shorten the development time of the team, contribute to the revitalization of software in our country!

Note: Of course, we should cultivate a lot of abilities,The basic knowledge should be solid, the idea of software engineering should be strengthened, and the sense of teamwork should be cultivated .........I am only targeting one aspect here!