My views on rapid development-to my friends who are constantly declining in development efficiency (2)

I wrote a lot last time,

There are also many opponents.

However, the number of applicable persons is quite small.

There is a dim sum, but at least a few summary for yourself, but also for interested friends,

Core:The system that can be used is very fast.

First, summarize three ideas:

1. Develop available systems as soon as possibleThe time for developing a perfect system is 10 times or more than one hundred times the time of a usable system,
   A complete design is a waste of time. In turn, after the system is developed, you naturally know where to perfect it.
   Don't be confused. An infinite nightmare. It will be slow and imperfect to develop.
2. Do not change the technology before the project is completedUnless the application of this technology has a profound impact on the progress
   Win3.1-> Win95-> WINXP-> winvista, there is no doubt that every generation is improving, but Vista, which takes the longest time, may not be able to please customers,
   A deliberate modification will bring about a new generation nightmare. the result may be a good system, but the loss of customers, time, and money cannot be measured.
3. PracticalThe messy concepts are dazzling, but sometimes they are not what we need

Finally, several methods are proposed:

1. Learn moreThe customer doesn't necessarily mean what the customer wants, because they don't understand it. A better execution method can be selected only when you have a detailed understanding of the requirements.
2. Function blocks can be independent.Easy division of labor, easy to modify, and easy to combine.
3. Reserved extension InterfaceDon't rewrite several places to add a simple logic.
4. Make preparations before commencementYou have to prepare the items to use.

The text is reduced, and the link is well compared.Article,

The revised version of crazy code is written to webmasters of Web2.0.

Of course, I am not saying that I am not good. On the contrary, I think that performance is sometimes very secondary in the early and middle stages of the development process (before we can see the implementation of the entire project,

There is no need to emphasize it, and it will be very troublesome for developers to deal with it at the beginning.

After the development is complete, check and maintain before, or even after the launch, the gap will not be very large.