The Art of UNIX Programming
by Eric S. Raymond · 22 Sep 2003 · 612pp · 187,431 words
number have been touted and sold as a cure for this problem. All have failed as cures, if only because they ‘succeeded’ by escalating the normal level of program complexity to the point where (once again) human brains could barely cope. As Fred Brooks famously observed [Brooks], there is no silver bullet. The only way to
…
might be a major contributor to the order-of-magnitude (or larger) variations in effectiveness observed by Fred Brooks and others. Compactness and Orthogonality Code is not the only sort of thing with an optimal chunk size. Languages and APIs (such as sets of library or system calls) run up against the same sorts of
…
as Thin Glue The C language itself is a good example of the effectiveness of thin glue. In the late 1990s, Gerrit Blaauw and Fred Brooks observed in Computer Architecture: Concepts and Evolution [BlaauwBrooks] that the architectures in every generation of computers, from early mainframes through minicomputers through workstations through PCs, had tended to
…
Specification Level Upwards The programmer at wit's end ... can often do best by disentangling himself from his code, rearing back, and contemplating his data. Representation is the essence of programming. -- Fred Brooks The Mythical Man-Month, Anniversary Edition (1975-1995), p. 103 In Chapter 1 we observed that human beings are better
…
may sound, come from established hacker jargon described in [Raymond96]. [115] The distinction between accidental and optional complexity means that the categories we're discussing here are not the same as essence and accident in Fred Brooks's essay No Silver Bullet [Brooks], but they have common ancestry in philosophy. A Tale of Five Editors Now we
…
characteristic eloquence. Some of the book is available on the Web. [BlaauwBrooks] Gerrit A. Blaauw and Frederick P. Brooks. Computer Architecture: Concepts and Evolution. 1997. ISBN 0-201-10557-8. Addison-Wesley. [Bolinger-Bronson] Dan Bolinger and Tan Bronson. Applying RCS and SCCS. O'Reilly & Associates. 1995. ISBN 1-56592-117-8. Not just a cookbook,
…
on the Web. [BrooksD] David Brooks. Converting a UNIX .COM Site to Windows. 2000. Available on the Web. [Brooks] Frederick P. Brooks. The Mythical Man-Month. 20th Anniversary Edition. Addison-Wesley. 1995. ISBN 0-201-83595-9. [Boehm] Hans Boehm. Advantages and Disadvantages of Conservative Garbage Collection. Thorough discussion of tradeoffs between garbage-collected
The Computer Boys Take Over: Computers, Programmers, and the Politics of Technical Expertise
by Nathan L. Ensmenger · 31 Jul 2010 · 429pp · 114,726 words
and captured useful truths. When Frederick Brooks
…
Frederick Brooks
…
and political process as it is technical; cultivating skilled designers requires a comprehensive and balanced approach to education, training, and career development. As Frederick Brooks observed in his “No Silver Bullet
…
Frederick P. Brooks, “No Silver Bullet: Essence and Accidents
…
and Aspray, Computer, 199. 37. Frederick Brooks, cited in Campbell-Kelly and Aspray, Computer, 200; Emerson Pugh, Lyle Johnson, and John Palmer, IBM’s 360 and Early 370 Systems (Cambridge, MA: MIT Press, 1991). 38. Frederick P. Brooks
…
Frederick P. Brooks, “No Silver Bullet: Essence and Accidents of Software Engineering,” IEEE Computer 20, no. 4 (1987), 10–19. 43. F. Terry Baker and
…
Frederick Brooks
…
Frederick Brooks, “No Silver Bullet: Essence and
…
No Silver Bullet: Essence and
…
No Silver Bullet,”
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software
by Scott Rosenberg · 2 Jan 2006 · 394pp · 118,929 words
We need the stuff more than we hate it. So we dream of new and better things. The expert who in many ways founded the modern field of software studies, Frederick P. Brooks, Jr., wrote an influential essay in 1987 titled “No Silver Bullet,” declaring that, however frustrated we may be with the writing of computer programs
…
Every effort to improve the making of software is an effort to keep them tight. The earliest and best diagnosis of the problem of software time can be found in a 1975 book by Frederick Brooks, The Mythical Man-Month. Brooks was a veteran IBM programming manager who had seen firsthand the follies
…
every problem will be characterized quickly and the fix obvious to someone. Or, less formally, ‘Given enough eyeballs, all bugs are shallow.’ I dub this: ‘Linus’s Law.’” Raymond argued that this new style of network-powered open peer review had broken the back of Frederick Brooks’s cruel paradox. “To Brooks
…
what will make Chandler special is a new and unique approach to data. The uncertainty about exactly what this means seems to pop up as part of every decision, the ground on which we are trying to stand is still cooling.” Thirty years before, Frederick Brooks had observed, “The hard thing about
…
either blissfully ignorant of the past or recklessly confident of the future—blithely certain that this time things will be different. “All programmers are optimists,” Frederick Brooks wrote in 1975. “Perhaps the hundreds of nitty frustrations drive away all but those who habitually focus on the end goal. Perhaps it is
…
crashed a lot. It was a true prototype, designed to be milked for whatever lessons it could teach and then discarded. In any project that is introducing a new technology or design, Frederick Brooks had advised, “plan to throw one away,” because you almost certainly won’t get it right the first
…
a project often falls at the very beginning, when worlds of giddy possibility lie open, and before painful compromises have shut any doors. “The programmer, like the poet, works only slightly removed from pure thought-stuff,” Frederick Brooks wrote. “He builds his castles in the air, from air, creating by exertion of
…
objects and functions and modules, increasingly available under open source licenses that meant you could tinker with them and incorporate them for free. Programmers setting out on big new projects could stand on the shoulders of ever taller giants. But they still had to decide where they wanted to go. As Frederick Brooks put
…
it in his “No Silver Bullet” essay: “The hardest single part of
…
the final dozen stubbornly resist a fix week after week. Furthermore, whichever unreliable yardstick you grab, you wind up facing the uncomfortable truth that Frederick Brooks reported in The Mythical Man-Month: Productivity varies wildly from one programmer to the next, frequently by as much as a factor of ten.
…
precision than Watts Humphrey—a high priest of software management who led the IBM software team in the 1960s after Frederick Brooks’s departure, and then went on to found the Software Engineering Institute at Carnegie-Mellon and to father a whole alphabet soup’s worth of software development methodologies. “With manufacturing, armies
…
for trouble when it comes to the simple need to communicate with anyone else who isn’t also a geek. Around the same time that Frederick Brooks was writing The Mythical Man-Month, another programmer of that era, Gerald Weinberg, wrote a book titled The Psychology of Computer Programming. It was
…
of Michael Toy’s departure is working. Progress is taking place. Code is getting written. And here and there, in corners of the development team, you could even sense a little of that quality of urgency that Frederick Brooks called “hustle.” OSAF released Chandler 0.3 on February 26, 2004. The new release
…
in the middle of trying to deliver OS/360, an operating system for its new System/360 generation of mainframe computing—the fiasco that inspired Frederick Brooks’s seminal writing in The Mythical Man-Month. Before accepting the job of running the OS/360 team, Brooks already had one foot out
…
. But they are still—just as much as the little spreadsheets that Dan Bricklin and Mitch Kapor introduced to the world a quarter century ago—made of “thought-stuff” (to recall Frederick Brooks’s term). And so every piece of software that gets used gets changed as people decide they want to adapt
…
. “We are stuck with the evolutionary pattern created by a hundred, then ten thousand, then millions of computing theoreticians and practitioners and users,” he wrote. “There will be no starting over.” Frederick Brooks tells us to give up hunting for a silver bullet: Software’s complexity is not a removable quality but an
…
it is possible to write grand programs, noble programs, truly magnificent ones!” Knuth is, like Frederick Brooks, a religious man (he is also a devotee of the pipe organ). He has pursued the writing and publication of his Art of Computer Programming series across five decades with the obsessional purity of someone
…
As the technical process improves, we mistakenly conclude that we have solved our problems. But the human process surrounding the technical process remains frustrating and intractable. If, as Frederick Brooks said, “the hard thing about building software is deciding what to say, not saying it,” then it doesn’t matter how closely you
…
the History of Computing 14: 4 (1992), pp. 18–28. That article is available at http://www.dcs.warwick.ac.uk/~mck/Personal/CampbellKelly1992.pdf. Frederick P. Brooks, “No Silver Bullet: Essence and Accidents of Software Engineering,” Computer, 20: 4 (April 1987), pp. 10–19. Also reprinted in The Mythical Man-Month Anniversary Edition (Addison Wesley,
…
OSAF staffers attended was the O’Reilly Open Source Conference held in July 2003. Brooks’s Law can be found on p. 25 of Frederick Brooks, The Mythical Man-Month Anniversary Edition (Addison Wesley, 1995). “The very unit of effort . . . deceptive myth” is on p. 16. “Men
…
written”: Ibid., p. 185. “you can read the Iliad”: Ibid., p. 172. “One engineer I know”: Ibid., pp. 168–69. “All programmers are optimists”: Frederick Brooks, The Mythical Man-Month Anniversary Edition (Addison Wesley, 1995), p. 14. Kapor delivered his “Software Design Manifesto” at the 1990 PC Forum conference. It was
…
Web site at http://www.mcsweeneys.net/links/events/chriscobb. htm. Information about the Semantic Web and RDF is at http://www.w3.org/2001/sw/. “plan to throw one away” and “promise to deliver a throwaway”: Frederick Brooks, The Mythical Man-Month (Addison Wesley, 1995), pp. 115–16. “The programmer, like the
…
OOPSLA 2004. “We are stuck with the evolutionary pattern”: Robert N. Britcher, The Limits of Software (Addison Wesley, 1999), p. 190. “essential property” and following: Frederick Brooks, “No Silver Bullet: Essence and Accidents of Software Engineering,” Computer 20:4 (April 1987), pp. 10–19. “Computer science is in deep trouble”: Gerald Jay Sussman, “Robust Design Through
…
bin/article.cgi?file=/c/a/2006/03/21/MNGD8HRJ761.DTL. “the hard thing about building software”: Frederick Brooks, “No Silver Bullet: Essence and Accidents of Software Engineering,” Computer 20:4 (April1987), pp. 10–19. “The machines will become more and more”: Freeman Dyson spoke at the O’Reilly Open Source Conference, Portland, Oregon, July 2004.
Coders: The Making of a New Tribe and the Remaking of the World
by Clive Thompson · 26 Mar 2019 · 499pp · 144,278 words
Fred Brooks
…
and support groups for women studying CS, events that made them more visible to their fellow students. Admissions, too, changed; it no longer gave so much preference to students who’d been teen coders. There was no silver bullet
…
Fred Brooks
Smart and Gets Things Done: Joel Spolsky's Concise Guide to Finding the Best Technical Talent
by Joel Spolsky · 1 Jun 2007 · 194pp · 36,223 words
and you quadruple the number that make it past the remaining obstacles. And so on, and so forth. But there is no silver bullet
…
Frederick Brooks, The Mythical
…
no silver bullet: there are a whole lot of problems you’re going to have to solve and
…
Frederick Brooks, 10 N The No Asshole Rule: Building a Civilized Workplace and
Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems
by Martin Kleppmann · 16 Mar 2017 · 1,237pp · 227,370 words
and Joseph Yoder: “Big Ball of Mud,” at 4th Conference on Pattern Languages of Programs (PLoP), September 1997. [31] Frederick P Brooks: “No Silver Bullet – Essence and
Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems
by Martin Kleppmann · 17 Apr 2017
and Joseph Yoder: “Big Ball of Mud,” at 4th Conference on Pattern Languages of Programs (PLoP), September 1997. [31] Frederick P Brooks: “No Silver Bullet – Essence and
Coders at Work
by Peter Seibel · 22 Jun 2009 · 1,201pp · 233,519 words
you're making in your code. You won't get all of them, right? And the dynamic tools like Valgrind and its race detectors, that's great too. There's no silver bullet, as Brooks said, but there are better languages and we should migrate to them as we can. Seibel: To what extent should programming
…
the age of the book, the ideas are all still current. Another old one is Frederick Brooks's The Mythical Man Month. It's 40 years old and still as true today as when it was written. And it's just a joy to read. Everyone should read that. The main message of
…
to you? Do you think of yourself as a scientist or an engineer or a craftsman? Or something else entirely? Peyton Jones: Have you read Fred Brooks's paper about this, the one called, “The Computer Scientist as Toolsmith”? I reread it recently. It's very nice. I think it's
…
do you think was the good stuff? For me the good stuff was Knuth; Aho, Hopcroft, and Ullman. Gerald Weinberg on The Psychology of Computer Programming, which I think is still very readable today. Fred Brooks's Mythical Man-Month gave me some insights. In those days I haunted the computer-science book
…
to this table on the other side of the room, and spread out my papers and think. Or work at the whiteboard or something. Seibel: I read something where you paraphrased Fred Brooks's saying about flowcharts and tables, saying, “Show me your interfaces and I won't need your code because it'll be redundant
…
for—there was a lot of freedom. Software engineering came much later. There wasn't software engineering and there weren't big processes set up yet. On a subsequent project, the 360, run by Fred Brooks, which I wasn't involved with, the software was a huge crisis. The engineering on the 360
…
Ideas, Seymour A. Papert (Basic Books, 1993) The Mythical Man-Month: Essays on Software Engineering, Frederick P. Brooks (Addison-Wesley Professional, 1995) Principles of Compiler Design, Alfred Aho and Jeffrey Ullman (Addison-Wesley, 1977) “Proof of a Program: FIND”, C.A.R. Hoare in Communications of the ACM, Vol. 14, Issue 1 (ACM,
The Mythical Man-Month
by Brooks, Jr. Frederick P. · 1 Jan 1975 · 259pp · 67,456 words
Photo credit: © Jerry Markatos ABOUT THE AUTHOR Frederick P. Brooks, Jr., is Kenan Professor of Computer Science at the University of North Carolina at Chapel Hill. He is best known as the "father of the IBM System/360," having served as project manager for its development and later as manager of the Operating System/360
…
from 1964 through 1984. He has served on the National Science Board and the Defense Science Board. His current teaching and research is in computer architecture, molecular graphics, and virtual environments. The Mythical Man-Month Essays on Software Engineering Anniversary Edition Frederick P. Brooks, Jr. University of North Carolina at Chapel Hill ADDISON-WESLEY Boston • San
…
of the George C. Page Museum of La Brea Discoveries, The Natural History Museum of Los Angeles County. Cover designer: Diana Coe. The essay entitled, No Silver Bullet, is from Information Processing 1986, the Proceedings of the IFIP Tenth World Computing Conference, edited by H.-J. Kugler, 1986, pages 1069-1076. Reprinted with
…
. Library of Congress Cataloging-in-Publication Data Brooks, Frederick P., Jr. (Frederick Phillips) The mythical man-month : essays on software engineering / Frederick P. Brooks, Jr. — Anniversary ed. p. cm. Includes bibliographical references and index. ISBN 0-201-83595-9 1. Software engineering. I. Title. QA76.758.B75 1995 005.1'068—dc20 94-36653
…
an Anniversary Edition. We decided not to revise the original, but to reprint it untouched (except for trivial corrections) and to augment it with more current thoughts. Chapter 16 reprints "No Silver Bullet: Essence and Accidents of Software Engineering," a 1986 IFIPS paper that grew out of my experience chairing a Defense Science Board study
…
back into touch with real-world large software projects. The paper was reprinted in 1987 in the IEEE Computer magazine, which gave it wide circulation. "No Silver Bullet" proved provocative. It predicted that a decade
…
Hypothesis Chapter 11: Plan to Throw One Away Chapter 12: Sharp Tools Chapter 13: The Whole and the Parts Chapter 14: Hatching a Catastrophe Chapter 15: The Other Face Chapter 16: No Silver Bullet—Essence and Accident Chapter 17: "No Silver Bullet" Refired Chapter 18: Propositions of The Mythical Man-Month: True or False? Chapter 19: The Mythical
…
very powerful ways. Since machines are made for people, not people for machines, their use makes every form of sense, economic and human. No Silver Bullet-Essence and Accident in Software Engineering No Silver Bullet-Essence and Accident in Software Engineering There is no single development, in either technology or management technique, which by itself promises even one order
…
a monster of missed schedules, blown budgets, and flawed products. So we hear desperate cries for a silver bullet, something to make software costs drop as rapidly as computer hardware costs do. But, as we look to the horizon of a decade hence, we see no silver bullet. There is no single development, in
…
progress would be made stepwise, at great effort, and that a persistent, unremitting care would have to be paid to a discipline of cleanliness. So it is with software engineering today. Does It Have to Be Hard?—Essential Difficulties Not only are there no silver bullets now in view, the very nature of software
…
not the labor of representing it and testing the fidelity of the representation. We still make syntax errors, to be sure; but they are fuzz compared to the conceptual errors in most systems. If this is true, building software will always be hard. There is inherently no silver bullet. Let us consider the inherent
…
each prospect, including carefully selected apprenticeships with top designers, episodes of advanced formal education, and short courses, all interspersed with solo design and technical leadership assignments. Provide opportunities for growing designers to interact with and stimulate each other. "No Silver Bullet" Refired "No Silver Bullet" Refired Every bullet has its billet. WILLIAM III OF ENGLAND, PRINCE OF ORANGE Whoever
…
is, nor e'er shall be. ALEXANDER POPE, AN ESSAY ON CRITICISM Assembling a structure from ready-made parts, 1945 The Bettman Archive On Werewolves and Other Legendary Terrors "No Silver Bullet—Essence and Accidents of Software Engineering" (now Chapter 16) was originally an invited paper for the IFIP '86 conference in Dublin
…
of an almost comical creature. I hope this less garish picture will have the same salutary effect. There is Too a Silver Bullet—AND HERE IT IS! "No Silver Bullet" asserts and argues that no single software engineering development will produce an order-of-magnitude improvement in programming productivity within ten years (from the paper
…
is timely to see how this prediction is holding up. Whereas The Mythical Man-Month generated many citations but little argument, "No Silver Bullet" has occasioned rebuttal papers, letters to journal editors, and letters and essays that continue to this day.3 Most of these attack the central argument that there is no magical solution
…
often in optimism than in pessimism. I am, after all, a programmer by background, and optimism is an occupational disease of our craft. "NSB" says explicitly "As we look to the horizon of a decade hence, we see no silver bullet. . . . Skepticism is not pessimism, however. . . . There is no royal road, but there
…
program called STYLE that accomplishes such a result. See also D. D. McCracken and G. M. Weinberg, "How to write a readable FORTRAN program," Datamation, 18, 10 (Oct., 1972), pp. 73-77. Chapter 16 The essay entitled "No Silver Bullet" is from Information Processing 1986, the Proceedings of the IFIP Tenth World Computing Conference
…
.J., Prentice-Hall, 1971. Boehm, B. W., "A spiral model of software development and enhancement," Computer, 20, 5 (May, 1985), pp. 43-57. Chapter 17 Material quoted without citation is from personal communications. Brooks, F. P., "No silver bullet—essence and accidents of software engineering," in Information Processing 86, H, J. Kugler, ed. Amsterdam:
…
Elsevier Science (North Holland), 1986, pp. 1069^1076. Brooks, F. P., "No silver bullet—essence and accidents of software engineering," Computer 20,4 (April, 1987), pp. 10-19
Refactoring: Improving the Design of Existing Code
by Martin Fowler, Kent Beck, John Brant, William Opdyke and Don Roberts · 9 Mar 2012
and streamline a program. Suppose you as a developer buy into these advantages. You agree with Fred Brooks
…
No Silver Bullet: Essence and
Site Reliability Engineering: How Google Runs Production Systems
by Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy · 15 Apr 2016 · 719pp · 181,090 words
ZeroMQ
by Pieter Hintjens · 12 Mar 2013 · 1,025pp · 150,187 words
Code Complete (Developer Best Practices)
by Steve McConnell · 8 Jun 2004 · 1,758pp · 342,766 words
Beautiful Architecture: Leading Thinkers Reveal the Hidden Beauty in Software Design
by Diomidis Spinellis and Georgios Gousios · 30 Dec 2008 · 680pp · 157,865 words
Culture & Empire: Digital Revolution
by Pieter Hintjens · 11 Mar 2013 · 349pp · 114,038 words
The C++ Programming Language
by Bjarne Stroustrup · 2 Jan 1986 · 923pp · 516,602 words
Kill It With Fire: Manage Aging Computer Systems
by Marianne Bellotti · 17 Mar 2021 · 232pp · 71,237 words
Ship It!: A Practical Guide to Successful Software Projects
by Jared R. Richardson and William A. Gwaltney · 15 Mar 2005 · 203pp · 14,242 words
Clojure Programming
by Chas Emerick, Brian Carper and Christophe Grand · 15 Aug 2011 · 999pp · 194,942 words
Chaos Engineering: System Resiliency in Practice
by Casey Rosenthal and Nora Jones · 27 Apr 2020 · 419pp · 102,488 words
An Elegant Puzzle: Systems of Engineering Management
by Will Larson · 19 May 2019 · 227pp · 63,186 words