AnyProgramOnce deployed, it becomes obsolete. It is easier to modify the requirement specification to adapt to the program. If a program is useful, it is doomed to be replaced. If a program is useless, it will certainly have good documentation. Only 10% of all programsCodeWill be executed. The software expands until all resources are exhausted. Any program with some value may have at least one bug. The degree of prototype perfection is inversely proportional to the number of people examined. The inverse ratio will increase with the number of funds involved. The most serious problem of the software is discovered until it is converted into a product running for at least six months. Errors that cannot be detected are in an infinite variety of forms. The opposite is true for the ones that can be detected, and the definitions are very limited. Efforts to fix an error will increase exponentially over time. The complexity of the software continues to increase until it exceeds the endurance of the person who maintains the program. I don't know any programs of my own. They are written by others for months. There is a huge program in any small program. The earlier the encoding starts, the longer it takes. A careless project plan will take you three times more time to complete; a careful project plan will only take you two times more time. Adding manpower to a large project will delay the project. A program will complete at least 90%, but it will never be able to complete more than 95%. If you want to solve the problem automatically, you will get the trouble automatically. Develop a software that a fool will use. Only a fool is willing to use it. Users do not really know what to do in the software unless they have used it.
Source: http://cnbeta.com/articles/123618.htm
