Intrinsic quotes

From Motley Bytes Wiki
Jump to: navigation, search

Nigel_Cross

Conventional Problem Solving

"Conventional wisdom about problem-solving seems often to be contradicted by the behavior of expert designers. But designing has many differences from conventional problem-solving. ... we must be very wary about importing models of design behavior from other fields. Empirical studies of design activity have frequently found 'intuitive' features of design ability to be the most effective and relevant to the intrinsic nature of design. Some aspects of design theory, however, have tried to develop counter-intuitive models and prescriptions for design behavior."

Mihaly_Csikszentmihalyi

Autotelic

“The key element of an optimal experience is that it is an end in itself. Even if initially undertaken for other reasons, the activity that consumes us becomes intrinsically rewarding... When the experience is autotelic, the person is paying attention to the activity for its own sake; when it is not, the attention is focused on its consequences.”
  • Source: Mihaly Csikszentmihalyi in the book “Flow: The Psychology of Optimal Experience“, chapter “The Autotelic Experience”, page 67. Original content published by Harper Perennial Modern Classics in 1990. Kindle edition published by Harper Collins in 2008. ISBN: 978-0061876721.

Writing

“It is never a waste to write for intrinsic reasons. First of all, writing gives the mind a disciplined means of expression. It allows one to record events and experiences so that they can be easily recalled, and relived in the future. It is a way to analyze and understand experiences, a self-communication that brings order to them.”
  • Source: Mihaly Csikszentmihalyi in the book “Flow: The Psychology of Optimal Experience“, chapter “The Play of Words”, page 131. Original content published by Harper Perennial Modern Classics in 1990. Kindle edition published by Harper Collins in 2008. ISBN: 978-0061876721.

Tom_DeMarco

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

Edsger_Wybe_Dijkstra

Humble Programmers

"We shall do a much better programming job, provided that we approach the task with a full appreciation of its tremendous difficulty, provided that we stick to modest and elegant programming languages, provided that we respect the intrinsic limitations of the human mind and approach the task as Very Humble Programmers."
  • Source: Edsger Wybe Dijkstra in an article entitled The Humble Programmer. Written by Edsger W. Dijkstra. Published 1972 in Communications of the ACM, volume 15, number 10. DOI: 10.1145/355604.361591.

Gordon_Glegg

Engineering the Impossible

“One of the intriguing facts of the engineering profession is that it is not only possible but essential to do the impossible. But we must be careful to define what we mean by that word. We must distinguish between the relatively impossible and the intrinsically impossible. The relative impossibility is something which is impossible unless something else becomes possible. It always includes or implies a clause beginning 'unless'. The intrinsic impossibility contains an imprisoned self-contradiction within itself; it is absolutely impossible.”
  • Source: Glegg, G. L. (1969). The Design of Design. Cambridge, UK: Cambridge University Press. ISBN: 978-0-511-79996-9. Chapter 1 page 5.

Bernardo_Kastrup

Single Substrate

“Therefore, matter, psyche (including the psychoid) and spirit are all manifestations of a single substrate; they all share the same categorical basis; they are all constituted by the same intrinsic essence. Consequently, there is no room left for dualism.”
  • Source: From “Decoding Jung's Metaphysics: The Archetypal Semantics of an Experiential Universe”. Written by Bernardo Kastrup. Published by IFF Books, Washington DC. Kindle Edition. Page 85. Chapter 5.

Tim_Lister

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

Shoshana_Zuboff

Technology Change

“To fully grasp the way in which a major new technology can change the world... it is necessary to consider both the manner in which it creates intrinsically new qualities of experience and the way in which new possibilities are engaged by the often-conflicting demands of social, political, and economic interests in order to produce a 'choice.' To concentrate only on intrinsic change and the texture of an emergent mentality is to ignore the real weight of history and the diversity of interests that pervade collective behavior. However, to narrow all discussion of technological change to the play of these interests overlooks the essential power of technology to reorder the rules of the game and thus our experience as players. Moreover, these two dimensions of technological change, the intrinsic and the contingent, need to be understood, not separately, but in relation to one another. The same innovation that abstracts work and increases its intellectual content, thus enhancing the learning of lower level employees... can also, within the context of the choices by which it is adapted, be experienced as a new source of divisiveness and control.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 389. ISBN:0465032125.