Talking and writing Talking is natural. Writing is not. It may seem strange that the manual dexterity needed to hold a pencil—or use a keyboard—comes later than the lingual and mental dexterity needed to speak. But it does. Verlyn Klinkenborg, Several Short Sentences About Writing speech
Applause lights Most applause lights are much more blatant, and can be detected by a simple reversal test. For example, suppose someone says: We need to balance the risks and opportunities of AI. If you reverse this statement, you get: We shouldn’t balance the risks and opportunities of AI. Since the reversal sounds abnormal, the unreversed statement is probably normal, implying it does not convey new information. There are plenty of legitimate reasons for uttering a sentence that would be uninformative in isolation. “We need to balance the risks and opportunities of AI” can introduce a discussion topic; it can emphasize the importance of a specific proposal for balancing; it can criticize an unbalanced proposal. Linking to a normal assertion can convey new information to a bounded rationalist—the link itself may not be obvious. But if no specifics follow, the sentence is probably an applause light. Eliezer Yudkowsky, Rationality: From AI to Zombies speech
Perilous to be sure It would not be clear where the boundary of sanctioned speech lay until an attempt had been made to cross it and that attempt had failed. Such efforts Wittgenstein regarded with benevolence. He treated them as reconnaissance expeditions, perilous to be sure, but well worth the effort expended on them. H. Stuart Hughes, The Sea Change wordsexplorationspeech
Idiolect A Definition en.wikipedia.org Idiolect is an individual's unique use of language, including speech. This unique usage encompasses vocabulary, grammar, and pronunciation. An idiolect is the variety of language unique to an individual. This differs from a dialect, a common set of linguistic characteristics shared among a group of people. Things you didn't know you can be bad at languagepersonalityidentityexpressionspeech
Writing and Speaking An Essay by Paul Graham paulgraham.com Being a really good speaker is not merely orthogonal to having good ideas, but in many ways pushes you in the opposite direction...there's a tradeoff between smoothness and ideas. All the time you spend practicing a talk, you could instead spend making it better. writingspeechcommunicationpractice
The primacy of interpretation over sensation A Fragment by Mark Liberman languagelog.ldc.upenn.edu Our memory of exact word sequences usually fades more quickly than our memory of (contextually interpreted) meanings. More broadly, the exact auditory sensations normally fade very quickly; the corresponding word sequences fade a bit more slowly; and the interpreted meanings last longest. These generalizations can be overcome to some extent if the sound or the text has especially memorable characteristics. (And the question of what "memorable" means in this context is interesting.) memorysensesmeaningspeechwords
What's Wrong With This Model? A Chapter from The Design of Design by Frederick P. Brooks, Jr. What's wrong with the rational modelDeciding what to designEvaluating goodnessChanging constraintsThey just don't work that way+1 More
What's wrong with the rational model We Don’t Really Know the Goal When We Start We Usually Don’t Know the Decision Tree – We Discover It as We Go The Nodes Are Really Not Design Decisions, but Tentative Complete Designs The Goodness Function Cannot be Evaluated Incrementally The Desiderata and Their Weightings Keep Changing The Constraints Keep Changing Changing constraintsDeciding what to designThe situation talks back
Deciding what to design We Don’t Really Know the Goal When We Start The most serious model shortcoming is that the designer often has a vague, incompletely specified goal, or primary objective. In such cases, the hardest part of design is deciding what to design. I came to realize that the most useful service I was performing for my client was helping him decide what he really wanted. Today, we recognize that rapid prototyping is an essential tool for formulating precise requirements. Not only is the design process iterative; the design-goal-setting process is itself iterative. Knowing complete product requirements up front is a quite rare exception, not the norm. Therefore, goal iteration must be considered an inherent part of the design process. What's wrong with the rational model iteration
Evaluating goodness The Goodness Function Cannot be Evaluated Incrementally The Rational Model assumes that design involves a search of the decision tree, and that at every node, one can evaluate the goodness function of several downward branches. In fact, one cannot in general do this without exploring all the downward branches to all their leaves, which is possible in principle, but leads to a combinatorial explosion of alternatives in practice. What's wrong with the rational model
Changing constraints The Constraints Keep Changing The explicit listing of known constraints in the design program helps here. The designer can periodically scan the list, asking, “Can this constraint now be removed because the world has changed? Can it be entirely circumvented by working outside the design space?” What's wrong with the rational model constraints
They just don't work that way Perhaps the most devastating critique of the Rational Model, although perhaps the hardest to prove, is that most experienced designers just don’t work that way. “Conventional wisdom about problem-solving seems often to be contradicted by the behavior of expert designers. 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.” — Nigel Cross
We must outgrow it Why all this fuss about the process model? Does the model we and others use to think about our design process really affect our designing itself? I believe it does. I believe our inadequate model and following it slavishly lead to fat, cumbersome, over-features products and also to schedule, budget, and performance disasters. The Rational Model, in any of its forms, leads us to demand up-front statements of design requirements. It leads us to believe that such can be formulated. It leads us to make contracts with one another on the basis of enshrined ignorance. A more realistic process model would make design work more efficient, obviating many arguments with clients and much rework. The Waterfall Model is wrong and harmful; we must outgrow it.