No Silver Bullet

From Wikipedia, the free encyclopedia
(Redirected from Accidental complexity)

"No Silver Bullet—Essence and Accident in Software Engineering" is a widely discussed paper on software engineering written by Turing Award winner Fred Brooks in 1986.[1] Brooks argues that "there is no single development, in either technology or management technique, which by itself promises even one order of magnitude [tenfold] improvement within a decade in productivity, in reliability, in simplicity." He also states that "we cannot expect ever to see two-fold gains every two years" in software development, as there is in hardware development (Moore's law).


Brooks distinguishes between two different types of complexity: accidental complexity and essential complexity. This is related to Aristotle's classification. Accidental complexity relates to problems which engineers create and can fix. For example, modern programming languages have abstracted away the details of writing and optimizing assembly code, and eliminated the delays caused by batch processing, though other sources of accidental complexity remain. Essential complexity is caused by the problem to be solved, and nothing can remove it; if users want a program to do 30 different things, then those 30 things are essential and the program must do those 30 different things.

Brooks claims that accidental complexity has decreased substantially, and today's programmers spend most of their time addressing essential complexity. Brooks argues that this means shrinking all the accidental activities to zero will not give the same order-of-magnitude improvement as attempting to decrease essential complexity. While Brooks insists that there is no one silver bullet, he believes that a series of innovations attacking essential complexity could lead to significant improvements. One technology that had made significant improvement in the area of accidental complexity was the invention of high-level programming languages, such as Ada.[1]

Brooks advocates "growing" software organically through incremental development. He suggests devising and implementing the main and subprograms right at the beginning, filling in the working sub-sections later. He believes that programming this way excites the engineers and provides a working system at every stage of development.

Brooks goes on to argue that there is a difference between "good" designers and "great" designers. He postulates that as programming is a creative process, some designers are inherently better than others. He suggests that there is as much as a tenfold difference between an ordinary designer and a great one. He then advocates treating star designers equally well as star managers, providing them not just with equal remuneration, but also all the perks of higher status: large office, staff, travel funds, etc.

The article, and Brooks's later reflections on it, "'No Silver Bullet' Refined", can be found in the anniversary edition of The Mythical Man-Month.[2]

Related concepts[edit]

Brooks's paper has sometimes been cited in connection with Wirth's law, to argue that "software systems grow faster in size and complexity than methods to handle complexity are invented".[3]

See also[edit]


  1. ^ a b "No Silver Bullet—Essence and Accident in Software Engineering"
  2. ^ The Mythical Man-Month, chapter 17
  3. ^ Tim A. Majchrzak (2012). Improving Software Testing: Technical and Organizational Developments. Springer Science & Business Media. p. 4. ISBN 978-3-642-27464-0.

Further reading[edit]

External links[edit]