Eliminate quotes

From Motley Bytes Wiki
Jump to: navigation, search

Robert_N_Britcher

Important Development Things

“The single, most important thing is that the individual programmer needs to be given total responsibility and control of the programming, including its function... eliminate project design and review as an exhaustive and rigorous process. Most of the design and review should occur as the program is written. ... Monitor progress on the project by talking to the individual programmers as [code] is being written. ... You must trust developers on the project to create a good product. ... Sometimes there are failures. ... The important thing is to fail quickly so you have time to find another approach. ... Developers must also feel free to say what they think to their supervisor. ... Managers should be the best programmers; ...There should be no overtime pay. ... Use profit-sharing and bonuses to get awesome products. ... Developers should each get their own office. ... Eliminate the dress code. Avoid meetings at all costs. ... Writing software is a lot like writing a book. Almost anyone can write garbage; very few can write a best-seller.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 155-156.

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).

Arthur_Conan_Doyle

Holmesian Fallacy

“When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.”
  • Source: Words of the fictional character Sherlock Holmes. Written by Sir Arthur Conan Doyle in the short story “The Adventure of the Blanched Soldier”. Included in the book “The Case-Book of Sherlock Holmes”, published 1927 by John Murray, United Kingdom.
  • Notes: This passage is often referred to as “Holmesian fallacy”, “Sherlock Holmes fallacy”, or “process of elimination fallacy”.

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.

Edward_Yourdon

Prototyping Analysis Design

“Everyone knows the benefits of building a prototype for an end user who is unsure of his or her requirements, but prototyping cannot eliminate the need for formal analysis and design work on large, complex projects.”
  • Source: Edward Yourdon in the book “Decline and Fall of the American Programmer”. Published in 1992 by Prentice Hall. ISBN: 0-13-203670-3. Chapter 2, section 2.4, page 30.

Shoshana_Zuboff

World Lost or Gained

'“There is a world to be lost and a world to be gained. Choices that appear to be merely technical will redefine our lives together at work. This means more than simply contemplating the implications or consequences of a new technology. It means that a powerful new technology, such as that represented by the computer, fundamentally reorganizes the infrastructure of our material world. It eliminates former alternatives. It creates new possibilities. It necessitates fresh choices.“
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 5 (Introduction). ISBN:0465032125.

Information and Automating

“To the extent that technology is used only to intensify the automaticity of work, it can reduce skill levels and dampen the urge toward more participatory and decentralized forms of management... However, this approach cannot exploit the unique power of an informating technology. In contrast, an approach to technology deployment that emphasizes its informating capacity uses technology to do far more than routinize, fragment, or eliminate jobs. It uses the new technology to increase the intellectual content of work at virtually every organizational level, as the ability to decipher explicit information and make decisions informed by that understanding becomes broadly distributed among organizational members.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 243. ISBN:0465032125.