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
Deadlines are bullshit An Article contrariantruth.substack.com In software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil. External vs. internal deadlinesWhy are internal deadlines evil?Engineers who love their work Hofstadter's LawThe Thing-deadline calculusNever enough timeDriving engineers to an arbitrary date is a value destroying mistake bureaucracysoftwareprocesswork
External vs. internal deadlines When are deadlines necessary? Contractual obligations Technical liabilities (e.g., dependency EOL) Compliance, government, investors, and other external stakeholders What do all of these deadlines have in common? They are all important. They are all deadlines that cannot be missed. They are all external. When are deadlines evil? Your manager says you have a deadline Your software development methodology says you have deadlines What do all of these deadlines have in common? None of them are important. They are arbitrary. They are all internal. They are all bullshit.
Why are internal deadlines evil? Estimation: When estimating engineering work a substantial time investment is required by an engineer in order to get an accurate estimate. Misaligned Incentives: There is an incentive to lie and give estimates much longer than the feature is truly expected to take. Low Morale: Deadlines are likely to be missed often. Repeated failure has a cost to the morale of the team. Micromanagement: Deadlines are wielded by middle managers as a whip to harass and annoy engineers working on features. High Stress: When engineers feel the pressure of other stakeholders holding deadlines over their heads it creates an environment of high stress. High Turnover: On teams with high turnover rates the best engineers have an easy time finding new work and leave quickly, the worst engineers have a difficult time finding work and remain. This selects for a lower quality team over time.
Engineers who love their work The resolution is simple. Never have internal deadlines. Operate on a prioritized and ordered list of features. Estimate only when necessary to prioritize and do so in a t-shirt sizing way. Trust your engineers and they will begin to love their work. Engineers who love their work are happy and productive. Building is never a straight line