Engineering quotes

From Motley Bytes Wiki
Jump to: navigation, search

Contents

Isaac_Asimov

Engineering

“Science can amuse and fascinate us all, but it is engineering that changes the world.”
  • Source: Isaac Asimov, chapter epigraph in Isaac Asimov’s Book of Science and Nature Quotations, edited by Isaac Asimov and Jason A. Shulman, published in 1988 by Weidenfeld and Nicolson, New York. Chapter 22, page 78. ISBN 1-555-84111-2.

Friedrich_Ludwig_Bauer

Need for Software Engineering

“What we need is Software Engineering.”
  • Source: Friedrich Ludwig Bauer's words at the end of 1967 within the NATO Science Committee charged with assessing the entire field of Computer Science. First generally recorded use of the term software engineering. Bauer also used the term in 1968 in a NATO conference in Garmisch-Partenkirchen, Germany. Reported on page 119 of the book entitled Origins and Foundations of Computing. Written by Friedrich Ludwig Bauer. Published by Springer in 2010. New York, NY. ISBN: 9783642425639.

Tinkering versus Engineering

“The time has arrived to switch from home-made software to manufactured software, from tinkering to engineering.”
  • Source: Quoted in the book entitled Mechanizing Proof: Computing, Risk, and Trust by Donald Mackenzie. Published in 2001 by Massachusetts Institute of Technology. ISBN: 0262133938.

Software Engineering Too Difficult

“Software engineering is the part of computer science which is too difficult for the computer scientist.”
  • Source: [Bauer; 1972]. A paper entitled Software Engineering. Written by Friedrich Ludwig Bauer. Published 1972 in Information Processing 71: Proceedings of Ifip Congress 1971, volume 1. ISBN: 9780720420630.

Software Engineering Definition

“(Software engineering is the) establishment and use of sound engineering principles to obtain economically software that is reliable and works on real machines efficiently.”
  • Source: [Bauer; 1972]. A paper entitled Software Engineering. Written by Friedrich Ludwig Bauer. Published 1972 in Information Processing 71: Proceedings of Ifip Congress 1971, volume 1. ISBN: 9780720420630.

Arthur_Bloch

Murphy's Law

“If anything can go wrong, it will.”
  • Source: Attributed to Edward A Murphy, reported in the book “Murphy's Law and Other Reasons Why Things Go Wrong” written by Arthur Bloch, first edition published in 1977 by [Price/Stern/Sloan](Los Angeles, California). ISBN-10: 0843104287. ISBN-13: 978-0843104288. Chapter ‘Murphology’, page 11.

Robert_N_Britcher

Programming and Engineering

“Some aspects of programming will remain forever beyond the grasp of classical engineering. Programming is too much like writing, too personal and private, too much under the spell of hyperbole, marketing, and self-aggrandizement.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 208.

Knowing Versus Doing

“We should not give up because there is no unified field theory of software engineering. The elements may not be easy to implement, but they are relatively simple, especially when compared with the study of proteins. ... The problem is not that we do not know enough. The problem is that we do not practice what we know.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 209.

Fred_Brooks

Brooks' Law

“Adding manpower to a late software project makes it later.”
  • Source: Brooks Jr., F. P. (1995). The Mythical Man-Month - Essays on Software Engineering (Anniversary Edition) | 1975/1995 (Anniv.). Boston. MA: Addison-Wesley. ISBN: 0201835959. Chapter 2, page 25. Known as Brooks' Law.

Tables versus Flowcharts

“Show me your flowcharts and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won't usually need your flowcharts; they'll be obvious.”
  • Source: Brooks Jr., F. P. (1995). The Mythical Man-Month - Essays on Software Engineering (Anniversary Edition) | 1975/1995 (Anniv.). Boston. MA: Addison-Wesley. ISBN: 0201835959. Chapter 9, page 102.

Rapid Prototyping

“Today the software engineering discipline is much more sophisticated. We recognize that rapid prototyping is an essential tool for formulating precise requirements. Not only is the design process iterative; the design-goal-setting process is itself iterative.”
  • Source: Brooks Jr., F. P. (2010). The Design of Design. Upper Saddle River, NJ: Addison-Wesley. ISBN: 978-0-201-36298-5. Chapter 3, page 23.

Rational Model

“Perhaps the most devastating critique of the Rational Model, although perhaps the hardest to prove, is that most experienced designers just don’t work that way.”
  • Source: Brooks Jr., F. P. (2010). The Design of Design. Upper Saddle River, NJ: Addison-Wesley. ISBN: 978-0-201-36298-5. Chapter 3, page 30.

Waterfall Model

“The Waterfall Model is wrong and harmful, we must outgrow it.”
  • Source: Brooks Jr., F. P. (2010). The Design of Design. Upper Saddle River, NJ: Addison-Wesley. ISBN: 978-0-201-36298-5. Chapter 3, page 34.

Edward_Emil_David

Software Engineer Training

"The problem of how the software engineers will get their practice is precisely the same as in other fields of engineering, and is insoluble. This is recognized in industry, where one makes sure that the young engineers coming in will get the proper kind of experience in time."

Competitive Rush

"Computing has one property, unique I think, that seriously aggravates the uncertainties associated with software efforts. In computing, the research, development, and production phases are often telescoped into one process. In the competitive rush to make available the latest techniques, such as on-line consoles served by time-shared computers, we strive to take great forward leaps across gulfs of unknown width and depth."

W_Edwards_Deming

Statistical Methods

"Statistical methods had taken fire in America around 1942, following a series of ten-day intensive courses for engineers, initiated by Stanford University on a suggestion from this author. The war department also gave courses at factories of suppliers. Brilliant applications attracted much attention, but the flare of statistical methods by themselves, in an atmosphere in which management did not know their responsibilities, burned, sputtered, fizzled and died out."
  • Source: W. Edwards Deming. Quality, Productivity and Competitive Position (1982) p. 101.

Edsger_Wybe_Dijkstra

Effective Reasoning

“The required techniques of effective reasoning are pretty formal, but as long as programming is done by people that don't master them, the software crisis will remain with us and will be considered an incurable disease. And you know what incurable diseases do: they invite the quacks and charlatans in, who in this case take the form of Software Engineering gurus.”

Software Crisis

“The turning point was the Conference on Software Engineering in Garmisch, October 1968, a conference that created a sensation as there occurred the first open admission of the software crisis.”

Peter_Drucker

Drucker's Law

“Engineers speak half–jokingly about Murphy's Law: 'If anything can go wrong, it will.' But complexity stands under a second law as well. Let me call it Drucker's law: 'If one thing goes wrong, everything else will, and at the same time.'”
  • Source: Peter F. Drucker, Management: Tasks, Responsibilities, Practices, New York: Harper & Row, 1973. p. 681.

Albert_Einstein

Magnificent Applied Science

“Why does this magnificent applied science which saves work and makes life easier bring us so little happiness? The simple answer runs: Because we have not yet learned to make sensible use of it. In war it serves that we may poison and mutilate each other. In peace it has made our lives hurried and uncertain. Instead of freeing us in great measure from spiritually exhausting labor, it has made men into slaves of machinery, who for the most part complete their monotonous long day's work with disgust and must continually tremble for their poor rations... It is not enough that you should understand about applied science in order that your work may increase man's blessings. Concern for the man himself and his fate must always form the chief interest of all technical endeavours; concern for the great unsolved problems of the organization of labor and the distribution of goods in order that the creations of our mind shall be a blessing and not a curse to mankind. Never forget this in the midst of your diagrams and equations.”
  • Source: Albert Einstein [Speaker];
    • 1950-02-16 [Speech/Date]; California Institute of Technology [Location]; CalTech students [Audience];
    • 1950-02-17 [Reporting/Article/Date]; “Einstein Sees Lack in Applying Science” [Title]; Anonymous [Article/Author]; New York Times [Reporting/Newspaper]; 8 [Page];

David_Epstein

Ill-Defined Problems

“Human intuition, it appears, is not very well engineered to make use of the best tools when faced with what the researchers called ‘ill-defined problems.’”
  • Source: David Epstein in the book “Range: Why Generalists Triumph in a Specialized World”. Published 2019 by Riverhead Books. Chapter 5, page 106. ISBN 978-0735214484.

Samuel_C_Florman

Drudgery

“Once the common man was released from drudgery, the engineers reasoned, he would inevitably become educated, cultured and ennobled, and this improvement in the race would also be to the credit of the engineering profession. Improved human beings, of course, would have to be happier human beings.”
  • Source: From the book “The Existential Pleasures of Engineering” by {Samuel C. Florman}. Second edition published in 1994 by {St. Martin's Press}, New York, NY. First edition published in 1976. Kindle edition published in 2023. E-book ISBN 978-1466842366. Chapter 1, page 6.

Irrationality

“So for the foreseeable future man’s irrationality — which engineering philosophers have seen fit to ignore — will have to be taken very seriously into account. In retrospect, the ideals and dreams of engineering’s Golden Age seem foolish and immature.”
  • Source: From the book “The Existential Pleasures of Engineering” by {Samuel C. Florman}. Second edition published in 1994 by {St. Martin's Press}, New York, NY. First edition published in 1976. Kindle edition published in 2023. E-book ISBN 978-1466842366. Chapter 2, page 16.

Social Responsibility

“For if ever there was a group dedicated to — obsessed with — morality, conscience, and social responsibility, it has been the engineering profession. Practically every description of the practice of engineering has stressed the concept of service to humanity.”
  • Source: From the book “The Existential Pleasures of Engineering” by {Samuel C. Florman}. Second edition published in 1994 by {St. Martin's Press}, New York, NY. First edition published in 1976. Kindle edition published in 2023. E-book ISBN 978-1466842366. Chapter 3, page 19.

Moral Absolute

“We will search in vain for a single engineering moral absolute acceptable to the entire profession.”
  • Source: From the book “The Existential Pleasures of Engineering” by {Samuel C. Florman}. Second edition published in 1994 by {St. Martin's Press}, New York, NY. First edition published in 1976. Kindle edition published in 2023. E-book ISBN 978-1466842366. Chapter 3, page 22.

Mistakes

“Human error, lack of imagination, and blind ignorance. The practice of engineering is in large measure a continuing struggle to avoid making mistakes for these reasons.”
  • Source: From the book “The Existential Pleasures of Engineering” by {Samuel C. Florman}. Second edition published in 1994 by {St. Martin's Press}, New York, NY. First edition published in 1976. Kindle edition published in 2023. E-book ISBN 978-1466842366. Chapter 3, page 33.

Emotional Fulfillment

“The nature of engineering has been misconceived. Analysis, rationality, materialism, and practical creativity do not preclude emotional fulfillment; they are pathways to such fulfillment. They do not ‘reduce’ experience, as is so often claimed; they expand it. Engineering is superficial only to those who view it superficially. At the heart of engineering lies existential joy.”
  • Source: From the book “The Existential Pleasures of Engineering” by {Samuel C. Florman}. Second edition published in 1994 by {St. Martin's Press}, New York, NY. First edition published in 1976. Kindle edition published in 2023. E-book ISBN 978-1466842366. Chapter 8, page 101.

Woodie_Flowers

Die Proud

“I want to die proud of having been an engineer... that can happen only if we engineers behave ethically.”
  • Source: Book/Contributor=Woodie Flowers; Book/Title=“Ethics in Engineering Practice and Research”; Contribution/Placement=Forward; Book/Author={C. Whitbeck}; Book/Publication/Date=2011; Edition=2nd; Publisher=Cambridge University Press; Location=New York, NY.

Keywords: Engineering_quotes Death_quotes Pride_quotes Ethics_quotes

Gordon_Glegg

Engineering the Impossible

“One of the intriguing facts of the engineering profession is that it is not only possible but essential to do the impossible. But we must be careful to define what we mean by that word. We must distinguish between the relatively impossible and the intrinsically impossible. The relative impossibility is something which is impossible unless something else becomes possible. It always includes or implies a clause beginning 'unless'. The intrinsic impossibility contains an imprisoned self-contradiction within itself; it is absolutely impossible.”
  • Source: Glegg, G. L. (1969). The Design of Design. Cambridge, UK: Cambridge University Press. ISBN: 978-0-511-79996-9. Chapter 1 page 5.

Engineering Stars

“A scientist can discover a new star but he cannot make one. He would have to ask an engineer to do it for him.”
  • Source: Glegg, G. L. (1969). The Design of Design. Cambridge, UK: Cambridge University Press. ISBN: 978-0-511-79996-9. Introduction.

Engineering Qualifications

“If you can do maths, engineering is waiting for you... There is one overriding qualification: you will never be a good engineer if you are frightened by hard work or responsibility.”
  • Source: Glegg, G. L. (1969). The Design of Design. Cambridge, UK: Cambridge University Press. ISBN: 978-0-511-79996-9. Chapter 2, page 25.

Engineers and Designers Are Human

“Throughout this book we have talked about 'designers' and 'engineers' and sought, by analysing their work, to find general and helpful maxims. But there is a danger in doing this, for we may forget that a 'designer' or 'engineer' is first and foremost a human being. A human being who designs or engineers has, in addition, a wide range of complicated and interacting emotions. It is easy to become emotionally involved in a new invention and so resent criticism of it even when that criticism, if heeded, would turn a failure into a success. Confidence may be blinded by conceit or undermined by an inferiority complex. History has shown that many new inventions were not inventions at all; they were re-inventions. The idea was not new but the determination to press through with it was. Character is the foundation of ability. Develop as large a safety margin as you can against such things as laziness, impatience, prejudice and arrogance and all the other human failings that inhibit constructive achievement in all spheres, especially that of creative engineering design.”
  • Source: Glegg, G. L. (1969). The Design of Design. Cambridge, UK: Cambridge University Press. ISBN: 978-0-511-79996-9. Chapter 6, page 92.

Eugene_Grace

Great Engineers

“Thousands of engineers can design bridges, calculate strains and stresses, and draw up specifications for machines, but the great engineer is the man who can tell whether the bridge or the machine should be built at all, where it should be built, and when.”

Cooperation

“In college and universities each student is given problems to work out, always by himself, never in cooperation with others. The present-day method of education may be suitable enough for lawyers, doctors, ministers, etc., but it is certainly not suitable for men who are going to enter engineering, industry, commerce, or business of any kind, where the very soul of success is cooperation with others.”

Robert_Heinlein

Magic

“One man's ‘magic' is another man's engineering.”
  • Source: Written by Robert A. Heinlein in the book “Time Enough for Love”, published in 1973 by Putnam's Sons, ISBN: 0-399-11151-4. Page 250. Character: Lazarus Long.

Keywords: Man_quotes Magic_quotes Engineering_quotes

Grace_Hopper

Microsecond Nanosecond

“In total desperation, I called over to the engineering building, and I said, 'Please cut off a nanosecond and send it over to me'... At the end of about a week, I called back and said, 'I need something to compare this to. Could I please have a microsecond?”
  • Source: On demonstrating a billionth and then millionth of a second of electricity travel by cutting a piece of wire, in an interview on the CBS television program 60 Minutes (24 August 1986).

Patterson_Hume

University Software Experience

“What really worries me about software engineering is, do universities have to engage in large software projects in order to remain experts in the field of software engineering? Do they have to hire people who have had such experience with large projects, or do they have to have their professors go out and as consultants experience large software engineering projects? Then, when they come to exercise the students, do they have to have laboratories of some considerable consequence in software engineering exercises? Otherwise, who is to formulate principles of software engineering that can be used to train software engineers?”

Kenneth_W_Kolence

Software Not Physical

“We clearly do not now have an engineering capability comparable to those based on the physical sciences. Such a capability is what is implied by the term software engineering. But software is not a physical system, it is a description of what one describes how a given physical system (a computer of some sort) should act. Thus software is more akin to engineering drawings, either maintained on paper or within a computer. ... So probably it is incorrect to assume software engineering should be considered as a sibling in the family of the physical science based engineering disciplines.”

Software Engineer

“There are people who call themselves software engineers, and who build software systems that other people trust their lives to that software. So a great deal of progress has really been made since 1962 (when I first began considering myself as a software engineer) and in that respect toward what may be considered as a valid engineering capability. ... Using the term [Software Engineering] ... actually did, for the first time, provide programmers with a more professional description of what they were trying to do. In my opinion, that was a very good thing.”

Software Engineering Body of Knowledge

‘While software engineering may be based on good principles of design activities, it is not a physical science based engineering body of knowledge. So we have to build an engineering capability based on some other body of knowledge.”

Alexander_Kossiakoff et al.

Systems Engineering Function

“The function of systems engineering is to guide the engineering of complex systems.”
  • Source: Kossiakoff, Alexander; Sweet, William N.; Seymour, Samuel J.; Biemer, Steven M.. Systems Engineering Principles and Practice. Wiley. 2011. Kindle Edition. Section 1.1. Page 3.

Skeptical Positive Thinking

"The Power of Skeptical Positive Thinking... is meant to capture an important characteristic of successful systems engineering. The skeptical part is important to temper the traditional optimism of the design specialist regarding the probability of success of a chosen design approach. It is the driving force for the insistence of validation of the approach selected at the earliest possible opportunity. The other dimension of skepticism, which is directly related to the characteristic of positive thinking, refers to the reaction in the face of failure or apparent failure of a selected technique or design approach. Many design specialists who encounter an unexpected failure are plunged into despair. The systems engineer, on the other hand, cannot afford the luxury of hand wringing."
  • Source:Kossiakoff, Alexander; Sweet, William N.; Seymour, Samuel J.; Biemer, Steven M.. 'Systems Engineering Principles and Practice'. 2011. Wiley. Kindle Edition. Section 1.6 page 23.

Michael_Sean_Mahoney

Software Crisis and Software Engineering

“Let me say a bit more about the ‘software crisis’. It emerged in the late 1960s as an increasing number of large projects experienced large cost overruns, missed deadlines and failures to meet specifications. Some had to be canceled altogether. One response was calls for a discipline of ‘software engineering’”
  • Source: Michael S. Mahoney in a paper entitled The Histories of Computing(s). Published 2005 in Interdisciplinary Science Reviews, volume 30, number 2, pages 119–135. DOI: 10.1179/030801805X25927.

Undefined Software Engineering

“If one could not define 'software engineering' at the time, neither could one point to its practice. It was not coined to characterize an ongoing activity but rather to express a desire for one.”
  • Source: Michael S. Mahoney in a paper entitled The Roots of Software Engineering. Published 1990 in CWI Quarterly, volume 3, number 4.

Benoît_Mandelbrot

Engineering and Science

“Engineering is too important to wait for science.”
  • Source: Quoted in the article 'Fractal Finance' by Greg Phelan, Yale Economic Review, Fall, 2005.

Keywords: Engineering_quotes Science_quotes Importance_quotes Wait_quotes

Malcolm_McIlroy

Programs and Bridges

“There is a difference between writing programs and designing bridges.”

Edward_A_Murphy

Murphy's Law

Popular Version:
  “If anything can go wrong, it will.”
Original Version First Report:
  “If there are two or more ways to do something
   and one of those results in a catastrophe,
   then someone will do it that way”
Original Version Second Report:
  "If there is any way to do it wrong, he will."
  • Source:
    • Attributed to Edward A Murphy, reported in the book “Murphy's Law and Other Reasons Why Things Go Wrong” written by Arthur Bloch, first edition publish in 1977 by Price/Stern/Sloan, Los Angeles, California. ISBN-10: 0843104287. ISBN-13: 978-0843104288.
    • Attributed to Edward A Murphy, reported in the article “The Science of Murphy’s Law” written by Robert A. J. Matthews, published in 'Scientific America, volume 276 number 4, April 1997, DOI: 10.1038/scientificamerican0497-88.
    • Attributed to Edward A Murphy, reported in the book “The Making of a Scientist” by Anne Roe, published in 1953 by Dodd and Mead, New York, NY. ISBN 10: 0837171512. ISBN 13: 9780837171517.
  • Notes: An idea expressed by Edward Aloysius Murphy Jr. in 1949 in reference to rocket sled engineering work.

Keywords: Engineering_quotes Something_quotes Can_quotes Go_quotes Wrong_quotes Way_quotes Do_quotes One_quotes Two_quotes Result_quotes Catastrophe_quotes Someone_quotes Anything_quotes Murphy(topic)_quotes Law_quotes

John_David_North

Art of Engineering

“Aeroplanes are not designed by science, but by art in spite of some pretense and humbug to the contrary. I do not mean to suggest that engineering can do without science, on the contrary, it stands on scientific foundations, but there is a big gap between scientific research and the engineering product which has to be bridged by the art of the engineer.”
  • Source: John D. North, In John D. North, 'The Case for Metal Construction', The Journal of the Royal Aeronautical Society, (Jan 1923), 27, 11.

David_E_Nye

Programmers Perfectionists

“A single error in a program thousands of lines long prevented it from running correctly, and computer programmers became known as a fanatically exact group of perfectionists, working in an arcane specialty. Sociologists studying the ‘man-machine' interface found that a programmer's personality often changed after prolonged exposure to the computer, becoming severely logical and machine-like.”
  • Source: A book. Written by David E. Nye. Entitled 'Narratives and Spaces'. Published in 1997 by Univerity of Exeter Press, Exeter, UK. Hardback ISBN 0-85989-555-6. Paperback ISBN 0-85989-556-4. Chapter 10, page 164.

J_Robert_Oppenheimer

Technically Sweet

“When you see something that is technically sweet, you go ahead and do it and argue about what to do about it only after you've had your technical success. That is the way it was with the atomic bomb.”

Parkinson_and_Margulieux

Spatial Skills

“Higher spatial reasoning skills universally correlate with better STEM [Science Technology Engineering Mathematics] performance and achievement... This correlation is particularly interesting because spatial skills can be trained, and spatial skills training globally improves STEM performance and achievement.”
  • Source: From the journal article entitled “Improving CS Performance by Developing Spatial Skills”, in Communications of the ACM, volume 68, number 1, 2025-01. DOI:10.1145/3680409.

Richard_Pascale

Efficiency and Variation

“Corporations, in the name of efficiency, suppress variation by 'getting all the ducks in line'. To optimize productivity, they evolve highly refined and internally consistent operating systems. Payoff results - as long as the music lasts. But in the face of nontraditional competitors or major environmental discontinuities, all that streamlining and reengineering limits diversity, suppresses self-organization by those closest to the disruptive change, and curtails a bottom-up emergent response to cope more effectively... Nothing fails like success. Over-adaptive organizations become inflexible. Disruptive change leaves them as helpless as a beached whale.”
  • Source: Richard T. Pascale, Jerry Sternin, Monique Sternin (2010). “The Power of Positive Deviance: How Unlikely Innovators Solve the World's Toughest Problems”, p.190, Boston, MA: Harvard Business Press

Alan_Perlis

Software Engineering Competence

“It is a fact that there are software engineers around today who are quite competent. There are systems in many places which are quite stable and which provide magnificent service. It is also the case that there are large numbers of efforts, containing large numbers of programs and programmers, which have no software engineers on them, that is that people function as though they did not know how to build software.”
  • Note: Un-indexed continuation of quote: “I have a number of questions: 1. Is it possible to have software engineers in the numbers in which we need them, without formal software engineering education? 2. Is software engineering the same as Computer Science? 3. Is software engineering best provided by baccalaureate programs in universities? Or by adult education courses? Or by two year courses following the standard grade school education? 4. Do the people educated in these programs have a growing and future role in our society? 5. Will they be useful enough in a firm or government or university, and is their value such that they can distribute their talents in other activities, or must they always remain programmers? 6. What curriculum do we have in mind for software engineers, regardless of what level we choose to educate them? 7. Is software engineering really different from what we now call systems engineering?”

First Software Engineering Conference

“This is the first conference ever held on software engineering and it behooves us to take this conference quite seriously since it will likely set the tone of future work in this field”

Training

“Our problems arise from demands, appetites, and our exuberant optimism. They are magnified by the unevenly trained personnel with which we work. In our deliberations we will not, I believe, be able to avoid the education problem — software engineering does not exist without software engineers.”

Steven_Pinker

Psychology is Reverse Engineering

“Psychology is engineering in reverse.”
  • Source: Steven Pinker (1997). How the Mind Works. New York, NY: W. W. Norton. ISBN 978-0-393-06973-0; eISBN 978-0-393-06973-0. Chapter 1.

Keywords: Psychology_quotes Reverse_quotes Engineering_quotes

Jef_Raskin

Oppressive Computers

“Right now, computers, which are supposed to be our servant, are oppressing us.”
  • Source: Jef Raskin, on the potential to improve human-computer interaction, in interview with Berkeley Groks (3 March 2004).

Rittel_and_Webber

Planning Problems are Wicked Problems

“A great many barriers keep us from perfecting such a planning/governing system. Theory is inadequate for decent forecasting, our intelligence is insufficient to our tasks, plurality of objectives held by pluralities of politics makes it impossible to pursue unitary aims, and so on. The difficulties attached to rationality are tenacious, and we have so far been unable to get untangled from their web. This is partly because the classical paradigm of science and engineering - the paradigm that has underlain modern professionalism - is not applicable to the problems of open societal systems.”

Franz_Selig

Specification Feedback

“External specifications at any level describe the software product in terms of the items controlled by and available to the user. The internal design describes the software product in terms of the program structures which realize the external specifications. It has to be understood that feedback between the design of the external and internal specifications is an essential part of a realistic and effective implementation process. Furthermore, this interaction must begin at the earliest stage of establishing the objectives, and continue until completion of the product.”

Herbert_Simon

Engineering and Design

“Historically and traditionally, it has been the task of the science disciplines to teach about natural things: how they are and how they work. It has been the task of engineering schools to teach about artificial things: how to make artifacts that have desired properties and how to design.”

Design and Analysis

“In view of the key role of design in professional activity, it is ironic that in this century the natural sciences almost drove the sciences of the artificial from professional school curricula, a development that peaked about two or three decades after the Second World War. Engineering schools gradually became schools of physics and mathematics; medical schools became schools of biological science; business schools became schools of finite mathematics. The use of adjectives like 'applied' concealed, but did not change, the fact. It simply meant that in the professional schools those topics were selected from mathematics and the natural sciences for emphasis which were thought to be most nearly relevant to professional practice. It did not mean that design continued to be taught, as distinguished from analysis.”

Loss of Design Damage

“The damage to professional competence caused by the loss of design from professional curricula gradually gained recognition in engineering and medicine and to a lesser extent in business.”


Shannon_Vallor

Computer Does

“The computer did precisely what we told it to do, just not what we thought we had told it to do. Much of software engineering is simply figuring out how to close the gap between those two things.”
  • Source: From the book “The AI Mirror” by Shannon Vallor. Published 2024 by Oxford University Press. ISBN 978-0197759066. Chapter 2, page 45.

Gerald_Weinberg

Knowledge Came Slowly

“In ages past, the knowledge came very slowly, and one man in his life was not likely to see much change other than that wrought by nature. The controlled incorporation of arsenic into copper to make bronze took several thousand years to develop; the substitution of tin for the more dangerous arsenic took another thousand or two. In our modern age, laboratories turn out an alloy a day, or more, with properties made to order. The alloying of metals led to the rise and fall of civilizations, but the changes were too slow to be appreciated. A truer blade meant victory over the invaders, but changes were local and slow enough to be absorbed by a million tiny adjustments without destroying the species. With an alloy a day, we can no longer be sure. Science and engineering have been the catalysts for the unprecedented speed and magnitude of change. The physicist shows us how to harness the power of the nucleus; the chemist shows us how to increase the quantity of our food; the geneticist shows us how to improve the quality of our children. But science and engineering have been unable to keep pace with the second-order effects produced by their first-order victories. The excess heat from the nuclear generator alters the spawning pattern of fish, and, before adjustments can be made, other species have produced irreversible changes in the ecology of the river and its borders. The pesticide eliminates one insect only to the advantage of others that may be worse, or the herbicide clears the rain forest for farming, but the resulting soil changes make the land less productive than it was before. And of what we are doing to our progeny, we still have only ghastly hints. Some have said the general systems movement was born out of the failures of science, but it would be more accurate to say the general systems approach is needed because science has been such a success. Science and technology have colonized the planet, and nothing in our lives is untouched. In this changing, they have revealed a complexity with which they are not prepared to deal. The general systems movement has taken up the task of helping scientists unravel complexity, technologists to master it, and others to learn to live with it.”
  • Source: Weinberg, Gerald (2011-04-07). An Introduction to General Systems Thinking (Kindle Locations 264-267). Weinberg & Weinberg. Kindle Edition.