"There is no silver bullet" is fred brooks published in 1987 years of the classic papers on software engineering. The discussion emphasized the real silver bullet does not exist, the so-called silver bullet is the absence of any one technology or method can make the productivity of software engineering, a tenfold increase in a decade. brooks is best known for 1975 years in the book "Mythical Man-Month" - the Bible is known as software engineering. The core of this classic paper is often interpreted as a discussion of complex software engineering problems can not be solved by simple answers. Secondary and the necessary complexity In the discussion which, to a minor and necessary to discuss the complexity of the differences. The so-called secondary complexity is generated by the people themselves are the problem, and this type of problem can be solved. For example, the combination of writing and optimizing the complexity of the language is of secondary importance, it can borrow from the high-level programming language such as java instead. Complexity is necessary from the software itself derived from the problem to be solved, and can not be removed. If the software requires provides 30 different functions, then the thirty functions are necessary, these functions must be implemented to make. Software engineering problems that we have cleared most of the minor complexity, while the remaining (mainly complexity) can not be changed. Remove the secondary complexity in the progress of the largest high-level languages may have to be born, like fortran and java.
Translated by Google
No. 2
"There is no silver bullet" is Fred Brooks published in 1987 years of the classic papers on software engineering. The discussion emphasized the real silver bullet does not exist, the so-called silver bullet is the absence of any one technology or method can make the productivity of software engineering, a tenfold increase in a decade. Brooks is best known for 1975 years in the book "Mythical Man-Month" - the Bible is known as software engineering. The core of this classic paper is often interpreted as a discussion of complex software engineering problems can not be solved by simple answers. Secondary and the necessary complexity In the discussion which, to a minor and necessary to discuss the complexity of the differences. The so-called secondary complexity is generated by the people themselves are the problem, and this type of problem can be solved. For example, the combination of writing and optimizing the complexity of the language is of secondary importance, it can borrow from the high-level programming language such as Java to replace. Complexity is necessary from the software itself derived from the problem to be solved, and can not be removed. If the software requires provides 30 different functions, then the thirty functions are necessary, these functions must be implemented to make. Software engineering problems that we have cleared most of the minor complexity, while the remaining (mainly complexity) can not be changed. Remove the secondary complexity in the progress of the largest high-level language may be regarded as the birth, such as Fortran and Java.