Programming Essays - Software development in the "self-pressure"software,software development

Software development in the “self-pressure”

In the software sector, the number because there is no use of software engineering ideas fail 'case, many of them is the fear of failure, so now the idea of software engineering to software development, as well as efficient and successful theory endless, project managers , system architects, as well as work on all fronts attaches great importance to its staff, while another more programming Masters in thinking, more good management talent in practice! However, we note that some of the problems: project managers, programmers, as well as the development of key technologies from when they begin programming? They enter the development team, whether alone or with partners and the development of the software? . . . . . .

The answer is obviously, no one is prepared from their own procedures, they more or less independently develop the software, but in their independent development of software, there are no ideological thinking of the implementation of software? I think it is difficult to do so! Without pressure, it will be very difficult to exercise strict self-discipline, Take me, and friends recently in the development of a software sales company's Web site (Jsp + Struts), as is our own project, completely lost pressure, and perhaps their own poor self-discipline, the development of the very slow progress, although the hearts full of anticipation, Shoudexia agile is not worth having almost mentality, and formed a "slower than the" strange mentality, a result of the project development cost of increasing length. I started writing the progress of the proposed plan, who also wrote Renkuang said white writing, certainly not completed on time, then I think also the acquiescence, now in retrospect, that kind of thinking is extremely wrong! Of course, not all programmers like having the same on CSDN had seen many excellent programmers published technical articles, they have written a detailed plan and the progress of time constraints; there is blue sky Moderators writing a detailed schedule, and in a timely manner after completion of the work concluded, summed up the reasons for the extension project, which is doing a good job, is a good example for us!

After all, most people do is not very good! Therefore, I feel the need to talk about here, individuals or small groups in software development, we should be done the following:

1. Progress of the development of detailed plans (if not completed on time and also draw up);

2. Ensure development projects always consider software engineering ideas, as far as possible, in accordance with its process development;

3. Strive to improve their programming capabilities, and optimize the structure of the procedure (to complete the project on time);

4. If it is more than combat, I always keep fighting rush the situation, not to fall into the "slower than the" vicious circle;

5. Completion of the project, and do a good job summing up, accumulate experience for the next development.

I think we took jobs before the beginning of a good software development habit, then we really set foot on jobs, the corporation will adapt quickly to the development, shorten the development time team, as our country's contribution to the revitalization of software strength!

Note: Of course, we should develop the capacity of many, to a solid foundation of knowledge, strengthen the software engineering ideas, cultivate awareness ……… team I would only address one aspect!

Bookmark it: These icons link to social bookmarking sites where readers can share and discover new web pages.