Efficiency quotes

From Motley Bytes Wiki
Jump to: navigation, search

Friedrich_Ludwig_Bauer

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.

Tom_DeMarco and Tim_Lister

Cheeseburgers

"Development is inherently different from production. But managers of development and allied efforts often allow their thinking to be shaped by a management philosophy derived entirely from a production environment.
Imagine for the moment that you’re the manager of the local fast food franchise. It makes perfect sense for you to take any or all of the following efficient production measures:
- Squeeze out error. Make the machine (the human machine) run as smoothly as possible.
- Take a hard line about people goofing off on the job.
- Treat workers as interchangeable pieces of the machine.
- Optimize the steady state. (Don’t even think about how the operation got up to speed, or what it would take to close it down.)
- Standardize procedure. Do everything by the book.
- Eliminate experimentation—that’s what the folks at headquarters are paid for.
These would be reasonable approaches if you were in the fast food business (or any production environment), but you’re not. The 'make a cheeseburger, sell a cheeseburger' mentality can be fatal in your development area. It can only serve to damp your people’s spirits and focus their attention away from the real problems at hand. This style of management will be directly at odds with the work.
To manage thinking workers effectively, you need to take measures nearly opposite those listed above."
  • Source: Book: Entitled: Peopleware: Productive Projects and Teams. Edition: 3rd. Written by: Tom DeMarco; Tim Lister. Date published: 1987; 1999; 2013. Publisher: Addison-Wesley. Country: USA; GBR; CAN; DEU; FRA; ESP; ZAF; AUS; JPN; SGP; MEX. Language: en. ISBN: ISBN-13: 978-0-321-93411-6 (alk paper); 0-321-93411-3 (alk paper). Chapter: 2 (Make a Cheeseburger, Sell a Cheeseburger).

Peter_Drucker

Productivity and Efficiency

“The major incentive to productivity and efficiency are social and moral rather than financial.”
  • Source: Peter Drucker, The New Society (1950).

Yuval_Noah_Harari

Balance Truth and Order

“Simply increasing the speed and efficiency of our information technology doesn’t necessarily make the world a better place. It only makes the need to balance truth and order more urgent.”
  • Source: Yuval Noah Harari writing in his book ‘Nexus: A Brief History of Information Networks from the Stone Age to AI’. Published in 2024 by Random House. Kindle edition. Chapter 3 page 39. ISBN 978-0593734247.

Robert_K_Merton

Certified Knowledge

”The institutional goal of science is the extension of certified knowledge. The technical methods employed toward this end provide the relevant definition of knowledge: empirically confirmed and logically consistent predictions. The institutional imperatives (mores) derive from the goal and the methods. The entire structure of technical and moral norms implements the final objective. The technical norm of empirical evidence, adequate, valid and reliable, is a prerequisite for sustained true prediction; the technical norm of logical consistency, a prerequisite for systematic and valid prediction. The mores of science possess a methodologic rationale, but they are binding, not only because they are procedurally efficient, but because they are believed right and good. They are moral as well as technical prescriptions. Four sets of institutional imperatives – universalism, communism, disinterestedness, organized skepticism – comprise the ethos of modern science.”
  • Source: Robert King Merton, Social Theory and Social Structure (1957), 552-3.

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

Balance Efficiency and Generality

“Our progress, then, is measured by the balance we achieve between efficiency and generality. As the nature of our involvement with computation changes — and it does — the appropriate description of language changes; our emphasis shifts. I feel that our successor model will show such a change. Computer science is a restless infant and its progress depends as much on shifts in point of view as on the orderly development of our current concepts.”


Gerald_Weinberg

Programmers Are Human Beings

“If our experiences are any indication, each of them could be functioning more efficiently, with greater satisfaction, if he and his manager would only learn to look upon the programmer as a human being, rather than as another one of the machines.”
  • Source: Book Entitled: The Psychology of Computer Programming (Silver anniversary edition). Edition: Silver anniversary. Written By: Gerald Weinberg. Published originally: 1971. Republished: 2011.

Shoshana_Zuboff

Know-How

“The agenda for scientific management was to increase productivity by streamlining and rationalizing factory operation from cost accounting and supervision to the dullest job on the shop floor. Efficiency was the mania, and to achieve efficiency, it would be necessary to penetrate the labor process and force it to yield up its secrets. In order that effort be rationalized, the worker's skills had to be made explicit. In many cases, workers' perceptions of their own interests prevented them from articulating their know-how, but there was yet another involuntary barrier. These skills did not easily yield themselves to explication; they were embedded in the ways of the body, in the knacks and know-how of the craftworker.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 42. ISBN:0465032125.

Automated Evaluation

“The system automatically computed efficiency ratings for each worker by comparing the amount of time it took to complete a job had been priced. Such calculations with the amount of time for which it could have been generated only by a computer system, since 'we could never have enough clerks to compute these kinds of ratios.' The ratings were considered management information and were not accessible to the craftworkers. Many foremen cautioned against taking the ratings at face value. The most experienced craftsperson frequently was loaded with the most difficult assignments. That individual might show the worst efficiency rating simply because his or her assignments were the most complex and required more than the assigned time.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 331. ISBN:0465032125.