There are three situations that will definitely lead to failure of program design projects.
1. Manager of this project does not know about the software; 2. Project leaders responsible for the program code is not interested in writing code; 3. The programmer who writes code is temporarily hired, lacking loyalty to the project.
------------------------------------------------ "THE ZEN of Programming, by Geoffrey James,
I saw this sentence in the forum today, I feel that I need to add a sentence.
Designers are not sure about demand, I think it is always changed.
This condition leads to the third article above
Unfortunately, I am experiencing these modifications for a function may take 4 or 5 times, and each modification is very important. I really don't say it and more serious is to do PB's origin. Net and PB. Powerful, proposing some of the difficult requirements for Web, such as the column in DataGrid to be able to use the mouse to rearrange the most seriously, he thinks it is very simple, do not understand a "small" function to modify it actually A few days
Come back and forth is changed, the time and change time is 1 to 9, according to his requirements, maybe he will then want to change, it is scared all day, I am afraid that he has taken it again. The idea is really a sense of accomplishment, and some are just depressed, disappointed and depressed. There are still a lot ...
Our programmers are not high, give me a style book, I have completed this feature, and the new ideas of other new ideas have left the next version. We need it before the development. How is it so difficult?
We are just a small programmer, why do you want to pay for those poor management and design?
