Product quotes

From Motley Bytes Wiki
Jump to: navigation, search

F_Terry_Baker

Code Library

“The most important of these is a development support library which encourages the visibility and manageability of the product, as well as reduces clerical effort on the part of the programmers. The library is typically maintained and operated by a programming librarian who serves to control the programming assets and to provide the necessary services for both programmers and management. As a result of its use, the entire project is maintained in a centralized, up-to-date, visible form which makes its status immediately apparent to code-competent software managers and makes it possible for programmers to answer their questions directly without relying on others.”
  • Source: Baker, F. T. (1975). Software Management Through Improved Programming Technology. ACM ’75: Proceedings of the 1975 Annual Conference, 286–287. https://doi.org/10.1145/800181.810346

Program Ownership

“A program or program system is a group product and should be produced in a way which allows and encourages maximum knowledge of it by each person involved. Furthermore, the management responsible for its development should be able to determine its status directly and not depend on the programmer's description of his progress on an 'invisible product'.”
  • Source: Baker, F. T. (1975). Software Management Through Improved Programming Technology. ACM ’75: Proceedings of the 1975 Annual Conference, 286–287. https://doi.org/10.1145/800181.810346

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.

Fred_Brooks

Great Designers

“A little retrospection shows that although many fine, useful software systems have been designed by committees and built by multipart projects, those software systems that have excited passionate fans are those that are the products of one or a few designing minds, great designers.”
  • 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 16, page 202.

W_Edwards_Deming

Mass Inspection and Quality

"We cannot rely on mass inspection to improve quality, though there are times when 100 percent inspection is necessary. As Harold S. Dodge said many years ago, 'You cannot inspect quality into a product.' The quality is there or it isn't by the time it's inspected."
  • Source: W. Edwards Deming (1982) Out Of The Crisis. The MIT Press. (2e ed. 1986) p. 139.

Alexander_G_Fraser

Program Construction Sum

“One thing seems to be clear just now. It is that program construction is not always a simple progression in which each act of assembly represents a distinct forward step and that the final product can be described simply as the sum of many sub-assemblies.”

Arthur_L_Herman

Assembly Line Flexibility

“Ford had developed his assembly line to make a single product. Knudsen would show him how it could be used to make any product, anywhere.”
  • Source: Arthur L. Herman in the book “Freedom's Forge: How American Business Produced Victory in World War II”. Written by Arthur Herman. Published in 2012 by Random House, New York, NY. ISBN: 9780679604631 (ebook). Page 21.

Steve_Jobs

Show_Them

“We have a lot of customers, and we have a lot of research into our installed base. We also watch industry trends pretty carefully. But in the end, for something this complicated, it's really hard to design products by focus groups. A lot of times, people don't know what they want until you show it to them. That's why a lot of people at Apple get paid a lot of money, because they're supposed to be on top of these things.”

Kenneth_W_Kolence

Software Development Management

“Software product development requires (but is not itself sufficient) the design of rational and correctly integrated management and technical processes.”

Karl_Marx

Product of Mental Labor is Science

“The product of mental labor — science — always stands far below its value, because the labor-time necessary to reproduce it has no relation at all to the labor-time required for its original production.”
  • Source: Addenda, "Relative and Absolute Surplus Value" in Economic Manuscripts (1861-63)

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.

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

Patrick_Vlaskovits

Faster Horse

“However, even if Ford didn’t verbalize his thoughts on customers’ ostensible inability to communicate their unmet needs for innovative products — history indicates that Henry Ford most certainly did think along those lines... Henry Ford froze the design of the Model T... Ford had no compelling reason to innovate in any other sphere other than cost and price reduction... But everything changed with the onset of the innovations introduced by General Motors in the 1920s, which took the direct opposite of Henry Ford’s tack of “Any color … so long as it is black” and is best summed up by Alfred Sloan’s consumer-research driven “A Car for Every Purse and Purpose”... In 1921, the Ford Motor Company sold about 2/3 of all the cars built in the U.S. By 1926, this share had fallen to approximately 1/3. And in 1927, when Ford belatedly responded (at tremendous financial cost and internal strife) to changes in the market’s tastes and competitive innovation by shutting down production temporarily to re-tool his factories and bring the Model A to the market, that percentage fell to about 15%... Yes, some customers in certain types of businesses are quite capable of verbalizing precisely what sort of innovative product one could build and sell them. And of course, customers in other types of businesses are wholly incapable of verbalizing, with any sort of fidelity whatsoever, what they need and why they need it. An innovator should have understanding of one’s customers and their problems via empirical, observational, anecdotal methods or even intuition. They should also feel free to ignore customers’ inputs. Because by now it should be clear that Ford’s adherence to his vision of the mass-market car and how to materialize that vision was instrumental in both his early success in growing Ford Motor Company as well as his later failure to respond in a timely and effective manner to rapid innovation in the marketplace.”'

Shoshana_Zuboff

Life at the Data Interface

“Life at the data interface invites the worker into the abstract precincts of managerial work. It provides access to a broader view of the business as well as a deepened understanding of one's tasks and their role in the wider sphere of organizational functions. When work becomes synonymous with responsiveness to data, it engenders inquiry and dialogue, thus opening the way for workers to envision new possibilities and fresh alternatives to the reigning definitions of process, product, and organization.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 301. ISBN:0465032125.