Manager 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

Programmer Management

“With each programmer doing his own work in his own way, managers are so busy just trying to find out what's going on and why things don't fit together, that they don't have any opportunity to improve quality and reliability.”
  • 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.

Burke and Bailey

Recruiting Soft Skills

“Managers actually spend the vast majority of their recruitment time assessing a candidate’s soft skills.”
  • Source: An academic paper. Entitled Becoming an Adaptive Expert. Written by Quinn Burke; Cinamon Sunrise Bailey. Date published 2020. Published in: Communications of the ACM. Language: en. DOI: 10.1145/3366171.

DeMarco and Lister

People Not Modular

"Most of us as managers are prone to one particular failing: a tendency to manage people as though they were modular components."
  • 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). Part: I (Managing the Human Resource).

Seldom Manage That Way

"Most managers are willing to concede the idea that they’ve got more people worries than technical worries. But they seldom manage that way. They manage as though technology were their principal concern. They spend their time puzzling over the most convoluted and most interesting puzzles that their people will have to solve, almost as though they themselves were going to do the work rather than manage it. They are forever on the lookout for a technical whizbang that promises to automate away part of the work. The most strongly people-oriented aspects of their responsibility are often given the lowest priority."
  • 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: 1 (Somewhere Today, a Project Is Failing).

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

Error Quota

"For most thinking workers, making an occasional mistake is a natural and healthy part of their work. But there can be an almost Biblical association between error on the job and sin. This is an attitude we need to take specific pains to change. Speaking to a group of software managers, we introduced a strategy for what we think of as iterative design. The idea is that some designs are intrinsically defect-prone; they ought to be rejected, not repaired. Such dead ends should be expected in the design activity. The lost effort of the dead end is a small price to pay for a clean, fresh start. To our surprise, many managers felt this would pose an impossible political problem for their own bosses: 'How can we throw away a product that our company has paid to produce?' They seemed to believe that they’d be better off salvaging the defective version even though it might cost more in the long run. Fostering an atmosphere that doesn’t allow for error simply makes people defensive. They don’t try things that may turn out badly. You encourage this defensiveness when you try to systematize the process, when you impose rigid methodologies so that staff members are not allowed to make any of the key strategic decisions lest they make them incorrectly. The average level of technology may be modestly improved by any steps you take to inhibit error. The team sociology, however, can suffer grievously. The opposite approach would be to encourage people to make some errors. You do this by asking your folks on occasion what dead-end roads they’ve been down, and by making sure they understand that 'none' is not the best answer. When people blow it, they should be congratulated — that’s part of what they’re being paid for."
  • 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).

Kicking Ass

"Management is a complex enough thing to defy simple definition, but that nuance was lost on one senior manager we encountered at a professional society meeting in London. He summed up his entire view of the subject with this statement: 'Management is kicking ass.' This equates to the view that managers provide all the thinking and the people underneath them just carry out their bidding. Again, that might be workable for cheeseburger production, but not for any effort for which people do the work with their heads rather than their hands. Everyone in such an environment has got to have the brain in gear. You may be able to kick people to make them active, but not to make them creative, inventive, and thoughtful. Even if kicking people in the backside did boost their short-term productivity, it might not be useful in the long run. There is nothing more discouraging to any worker than the sense that his own motivation is inadequate and has to be 'supplemented' by that of the boss. The saddest thing about this management approach is that it’s almost always superfluous. You seldom need to take Draconian measures to keep your people working; most of them love their work. You may even have to take steps sometimes to make them work less, and thus get more meaningful work done."
  • 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

Intuitive Management

“The days of the 'intuitive' manager are numbered.”
  • Source: Peter Drucker, “The Practice of Management” New York,: Harper, 1st ed. 1954 ; Routledge, 2012, p. 93.

Keywords: Day_quotes Intuition_quotes Manager_quotes Number_quotes

Weaknesses and Strengths

"A man should never be appointed into a managerial position if his vision focuses on people's weaknesses rather than on their strengths."
  • Source: Peter Drucker, “The Practice of Management” New York,: Harper, 1st ed. 1954 ; Routledge, 2012, p. 157.

What a Manager Does

“A manager sets objectives - A manager organizes - A manager motivates and communicates - A manager, by establishing yardsticks, measures - A manager develops people.”
  • Source: Peter Drucker, “The Practice of Management” New York,: Harper, 1st ed. 1954 ; Routledge, 2012, p. 344.

Frederick_Winslow_Taylor

Kindly Interest

“...in order to have any hope of obtaining the initiative of his workmen the manager must give some special incentive to his men beyond that which is given to the average of the trade. This incentive can be given in several different ways, as, for example, the hope of rapid promotion or advancement; higher wages, either in the form of generous piece-work prices or of a premium or bonus of some kind for good and rapid work; shorter hours of labor; better surroundings and working conditions than are ordinarily given, etc., and, above all, this special incentive should be accompanied by that personal consideration for, and friendly contact with, his workmen which comes only from a genuine and kindly interest in the welfare of those under him.”
  • Source: F.W. Taylor, 1911. Principles of Scientific Management. New York and London, Harper & brothers. Chapter 1.

Gerald_Weinberg

Vending Machines

“When the vending machines had been in the common room, a large crowd always hovered around them — but not particularly for fol-de-rol, as the manager had so quickly assumed... Informal mechanisms always exist and it is dangerous to change things without understanding them.”
  • Source: Chapter 4. Weinberg, G. M. (2011). The Psychology of Computer Programming (Silver anniversary edition) | 1971. Weinberg & Weinberg.

Bad Managers and Good Programmers

“Bad managers are easier to find than good programmers.”
  • Source: Chapter 5. Weinberg, G. M. (2011). The Psychology of Computer Programming (Silver anniversary edition) | 1971. Weinberg & Weinberg.

Management Deskilling

“Even though the nth-level manager may have originally been a programmer, which is rare enough, he has almost certainly lost any programming ability by the time he reaches these heights. Given the rapid change of programming techniques and hardware, the higher-level manager becomes obsolete even if he retains the skills he originally had and keeps them sharply honed, for those languages and those machines are no longer in use. In a small survey of working programmers, only 15 percent of the first-line managers were thought to be as skillful as the programmers themselves, and none of the higher-level managers.”
  • Source: Chapter 6. Weinberg, G. M. (2011). The Psychology of Computer Programming (Silver anniversary edition) | 1971. Weinberg & Weinberg.

Shoshana_Zuboff

Manager Panic

“People at every organizational level -- managers, engineers, and operators -- each spent a good deal of time speculating on the sources of this dynamic and its ultimate consequences. One top manager maintained that the core of the problem was the lack of an alternative to the traditional managerial function. ‘The problem is that managers don't have skills and knowledge or a vision of their new role. They are asking, What is going to happen to me? And so they are in a panic.'”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 251. ISBN:0465032125.

Panopticon Coaching

“To be sure, some managers saw the enhanced certainty of their information about subordinates as an opportunity to accelerate learning and improve performance. They found that the data from the Overview System made it possible to survey a wide range of behavior for evidence of irregularities. To the extent that the sources of such irregularities could be discovered, the data could be used to 'coach' subordinates and to help them realign their behavior within acceptable standards... On the other hand, many of Cedar Bluff's managers were more interested in the possibility of obtaining foolproof data than in the opportunity of using such data for coaching. In the context of a conventional technology, managers had to rely on their subordinates for valid information. The quality of the data they received was likely to be a function of the quality of the reciprocal relationship they had established. In contrast, an informating technology could provide valid information under any conditions.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 324. ISBN:0465032125.