“Software people seem to have a love-hate relationship with metrics. On one hand, they despise and distrust anything that sounds or looks like a measurement. They are quick to point out the "flaws" in the arguments of anyone who talks about measuring software products, software processes, and (especially) software people. On the other hand, these same people seem to have no problems identifying which programming language is the best, the stupid things that managers do to "ruin" projects, and who's methodology works in what situations.”

— Edward V. Berard

Edward V. Berard (1998) " Metrics for object-oriented software engineering http://www.ipipan.gda.pl/~marek/objects/TOA/moose.html." The Object Agency, Inc.

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Software people seem to have a love-hate relationship with metrics. On one hand, they despise and distrust anything tha…" by Edward V. Berard?

Edward V. Berard 10

Jamie Zawinski (1968) American programmer

JWZ
http://www.jwz.org/doc/groupware.html
Groupware.

“In order to better understand object-oriented methodologies in general, it helps to understand the people who make up the "object-oriented community" itself. Far from being monolithic, there is a great deal of diversity within this community. Many object-oriented people, for example, seem to focus almost entirely on programming language issues. They tend to cast all discussions in terms of the syntax and semantics of their chosen object-oriented programming language. These people find it impossible (for all intents and purposes) to discuss any software engineering activity (e. g., analysis, design, and testing) without direct mention of some specific implementation language.
Outside of producing executable "prototypes", people who emphasize programming languages seldom have well-defined techniques for analyzing their clients' problems or describing the overall architecture of the software product. A great deal of what they do is intuitive. If they happen to have a natural instinct/intuition for good analysis or good design, their efforts on small-to-medium, non-critical projects can result in respectable software solutions.”

Edward V. Berard

Source: Essays on object-oriented software engineering (1993), p. 5

“It's clear that other problems such as religious fundamentalism, overpopulation, damage to the environment, and the domination of business over government, science, thought, and society, are much bigger than non-free software. But many other people are already working on them, and I don't have any great aptitude or ideas for how to address them. So it seems best for me to keep working on the issue of free software. Besides, free software does counter one aspect of business domination of society.”

Richard Stallman (1953) American software freedom activist, short story writer and computer programmer, founder of the GNU project

2000s, Thus Spake Stallman (2000)

“People who are really serious about software should make their own hardware.”

Alan Kay (1940) computer scientist

talk at Creative Think seminar, 20 July 1982 https://www.folklore.org/StoryView.py?project=Macintosh&story=Creative_Think.txt
1980s

“This is a software monopoly but at least it was written by people who care about security, so it's not like Microsoft's monopoly.”

Theo de Raadt (1968) systems software engineer

[OpenBSD's Theo de Raadt talks software security, Gedda, Rodney, Computerworld, http://www.computerworld.com.au/index.php/id;1498222899;fp;16;fpid;0, 2004-10-09, 2007-01-10]
speaking about OpenSSH.

“Most post-mortems of these software disaster projects have indicated that their problems would have been avoided or strongly reduced if there had been an explicit early concern with identifying and resolving their high-risk elements. Frequently, these projects were swept along by a tide of optimistic enthusiasm during their early phases, which caused them to miss some clear signals of high risk issues which proved to be the project's downfall later.
Enthusiasm for new software capabilities is a good thing. But it needs to be tempered with a concern for early identification and resolution of a project's high-risk elements, so that people can get these resolved early and then focus their enthusiasm and energy on the positive aspects of their software product.”

Barry Boehm (1935) American software engineer

Source: Software risk management: principles and practices (1991), p. 32

“The inability to isolate software components from each other is the main reason why many popular programming languages cannot be used for making robust system software.”

Joe Armstrong (1950–2019) British computer scientist

page 32
Making Reliable Distributed Systems in the Presence of Software Errors

“'The main argument for the term "open source software" is that "free software" makes some people uneasy. That's true: talking about freedom, about ethical issues, about responsibilities as well as convenience, is asking people to think about things they might rather ignore. This can trigger discomfort, and some people may reject the idea for that. It does not follow that society would be better off if we stop talking about these things.”

Richard Stallman (1953) American software freedom activist, short story writer and computer programmer, founder of the GNU project

1990s, Why "Free Software" is better than "Open Source" (1998)

“Software has to be designed by hackers who understand design, not designers who know a little about software. If you can't design software as well as implement it, don't start a startup.”

Paul Graham (1964) English programmer, venture capitalist, and essayist

"The Other Road Ahead" http://www.paulgraham.com/road.html, September 2001

“One of the difficulties in thinking about software is its huge variety. A function definition in a spreadsheet cell is software. A smartphone app is software. The flight management system for an Airbus A380 is software. A word processor is software. We shouldn't expect a single discipline of software engineering to cover all of these, any more than we expect a single discipline of manufacturing to cover everything from the Airbus A380 to the production of chocolate bars, or a single discipline of social organization to cover everything from the United Nations to a kindergarten. Improvement in software engineering must come bottom-up, from intense specialized attention to particular products.”

Michael A. Jackson (1936) British computer scientist

Michael A. Jackson in: K. De Grave (ed.) Formalism & Intuition in Software Development; A conversation with Michael A. Jackson conducted by Edgar G. Daylight and Bas van Vlijmen. 2015

Help us to complete the source, original and additional information

Edward V. Berard 10

Related quotes

Related topics