You are currently browsing the tag archive for the ‘bradshaw of the future’ tag.
goofy recently posted at bradshaw of the future about momentarily and some strange advice Grammar Girl sent out about it. Her advice:
“Don’t use momentarily to mean “in a moment”; you may confuse people. If you mean in a moment, say or write that. There’s no need to use momentarily in such cases, and doing so will irritate language purists.”
A quick note first: both the “in a moment” and “for a moment” meanings of momentarily have been around for 140 years, so the purists are completely unjustified in their complaint. Also, sure, there’s no need to use momentarily here, but then, there’s no need to ever use any given word. You can always paraphrase or re-write the sentence.
But the real question is two-fold: whether the benefits of using a questionable word outweighs its costs, and whether there’s a better word. You might think of this as a satisficing condition and an optimization condition.* And I suspect — although I don’t know if anyone’s studying this, or what they’ve found — that there’s some sort of a switch-off between the two methods depending on what production task you’re doing. When speed is one’s primary concern, presumably it’s sufficient to check that the word is beneficial; only when one has the luxury of time does full optimization kick in.
So is momentarily costly — i.e., will it confuse readers? goofy makes a good point about the potential confusion:
“If it’s more common for people to use momentarily to mean ‘in a moment’, then why advise people not to use it that way? It seems that Grammar Girl is essentially saying ‘don’t speak like everyone else in your speech community speaks.’ This seems counterproductive. [...] it might confuse people – but if most people already use it that way, why should it be confusing?”
He gives the example of a pilot saying “we’ll land momentarily”, and notes that no one except for an uncooperative speaker will think “that means ‘for a moment’!” But one might harbor doubts. Maybe no one will end up with that interpretation, but maybe they’ll be distracted by it during interpretation. Yeah, that’s certainly possible — but listeners are more adept at ignoring irrelevant ambiguities that we tend to give them credit for.
The famous example from introductory linguistics classes of this is Time flies like an arrow. The first time someone sees this sentence, it just sounds like a standard aphorism, and the only meaning they’re likely to seriously consider is “time moves in a swift manner, akin to an arrow”. But this sentence is ambiguous, of course, as almost all sentences are. Many of the words have different senses and different parts of speech that they can take on.
If we switch from a Noun-Verb-Preposition reading of time flies like to an Noun-Noun-Verb one, we get: “‘Time flies’ (as opposed to houseflies or gadflies) appreciate an arrow”. There’s also a Verb-Noun-Preposition reading, yielding an imperative: “as though you were an arrow, record the time the flies take to complete a task”. There are other interpretations, too, but none of these is likely enough, given our world-knowledge and parsing probabilities, to register in our minds. We can reasonably expect that Time flies like an arrow will be correctly understood, without time lost to alternative interpretations, by any audience that isn’t actively looking for implausible interpretations.
So too should we expect momentarily to be correctly understood; claiming to have difficulty with it marks the complainer, not the speaker, as the one who doesn’t understand language. As an editor, one generally ought to foolproof writing, looking for and eliminating potential (even if fairly unlikely) misinterpretations. But there’s a difference between editing to protect fools from ambiguity and editing to protect uncooperative readers from ambiguity. The former is difficult, but generally doable. The latter is often simple, but generally worthless.**
Let me conclude with a good question from Jonathon Owen in the comments on goofy’s post:
“And if the problem is simply that purists will be annoyed, why not direct our efforts to teaching the purists not to be annoyed rather than teaching everyone else to avoid offending this very small but very vocal set of peevers?”
*: “Satisificing” is an idea I’m fond of, though one that doesn’t get talked about much outside of human decision-making tasks. In the familiar optimization strategy, you’re trying to find the best of all possible options, whereas a satisficing strategy is just looking for any option that’s better than some threshold. For instance, if you go to the store with two dollars and need to buy milk, you can optimize by comparing multiple sub-$2 cartons before picking the best of that lot, or you can employ a satisifice by buying the first carton that costs less than two dollars.
Satisificing is generally faster and, if I remember my undergrad psych classes correctly, is common in human decision-making processes, especially when time is of the essence.
**: One exception, presumably, is in legal writing/contracts.