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
A Plea for Lean Software An Essay by Niklaus Wirth cr.yp.to Software's girth has surpassed its functionality, largely because hardware advances make this possible. The way to streamline software lies in disciplined methodologies and a return to the essentials. Measured by the number of its featuresEssential vs. nice to haveDependence is more profitable than educationThe most rewarding iterationsNever enough time A grossly obese set of requirementsFeatures and complexity softwareperformancefunction
Measured by the number of its features A primary cause of complexity is that software vendors uncritically adopt almost any feature that users want. Any incompatibility with the original system concept is either ignored or passes unrecognized, which renders the design more complicated and its use more cumbersome. When a system's power is measured by the number of its features, quantity becomes more important than quality. Every new release must offer additional features, even if some don't add functionality. featuresqualitycomplexity
Essential vs. nice to have Customers have trouble distinguishing between essential features and those that are just "nice to have." Examples of the latter class: those arbitrarily overlapping windows suggested by the uncritically but widely adopted desktop metaphor; and fancy icons decorating the screen display, such as antique mailboxes and garbage cans that are further enhanced by the visible movement of selected items toward their ultimate destination. These details are cute but not essential, and they have a hidden cost. / Increased complexity results in large part from our recent penchant for friendly user interaction. I've already mentioned windows and icons; color, gray-scales, shadows, pop-ups, pictures, and all kinds of gadgets can easily be added. Menus, Metaphors and Materials: Milestones of User Interface Designlittlebigdetails interfacesux
Dependence is more profitable than education A customer who pays—in advance—for service contracts is a more stable income source than a customer who has fully mastered a product's use. Customer dependence is more profitable than customer education. What I find truly baffling are manuals—hundreds of pages long—that accompany software applications, programming languages, and operating systems. Unmistakably, they signal both a contorted design that lacks clear concepts and an intent to hook customers. The design concept documentation
The most rewarding iterations Initial designs for sophisticated software applications are invariably complicated, even when developed by competent engineers. Truly good solutions emerge after iterative improvements or after redesigns that exploit new insights, and the most rewarding iterations are those that result in program simplifications. Evolutions of this kind, however, are extremely rare in current software practice—they require time-consuming thought processes that are rarely rewarded. Instead, software inadequacies are typically corrected by quickly conceived additions that invariably result in the well-known bulk. So that you can get feedback on it and make it betterTo anticipate all the uses and abuses agileiteration
Never enough time Time pressure is probably the foremost reason behind the emergence of bulky software. The time pressure that designers endure discourages careful planning. It also discourages improving acceptable solutions; instead, it encourages quickly conceived software additions and corrections. Time pressure gradually corrupts an engineer's standard of quality and perfection. It has a detrimental effect on people as well as products. Deadlines are bullshitThe Thing-deadline calculus