Mumbling Isn’t a Sign of Laziness, It’s a Clever Data-Compression Trick
nautil.us
nautil.us
Of course people make their language more efficient when using common words and phrases. "D'ja do it?" "Yeah." "K." "No prob."
But that's not mumbling.
I think of mumbling as generally being an expressed disinterest in being understood. Sometimes because the speaker doesn't understand what they're being asked to speak about, sometimes because they're shy and insecure about their words. Sometimes mumbling is a way to express derision or disinterest in the information or the person someone's speaking to. Lots of reasons.
Not clever. Kind of the opposite of clever. It's a time-waster compared to just flat-out saying "I don't know" or "I'm not sure" or "I don't care" or whatever.
Edit: also, "to speak incoherently" and "to fail to articulate" are both acceptable definitions of the word "mumble":
chasing is suggesting that when a person starts to mumble, which they seemed to define as speaking incoherently due to a variety of psychosocial circumstances- completely different from the article's definition- they are behaving irrationally and wasting time because the rational thing to do would be to directly and clearly state the reason, assuming the speaker is even aware of such a reason, that they began to mumble in the first place.
>If the output isn't coherent or fails to articulate such that the listener doesn't understand the message, then it's hardly adaptive.
Clipping, assimilation, etc. do not meet your criteria as they do not cause incomprehensibility. They may draw prescriptive criticism, but they do not deprive phrases of all conceivable meaning. Those are the types of phenomena that the article is discussing.
More to the point, when I say "adaptive" I am talking about the evolution of language. The winds of change. It isn't always "good" in an objective sense, but it never leads to a breakdown of meaning.
>incomprehensibility of mumbling.
Think of the definition used by the article as "failure to enunciate" and it should make more sense. Perhaps it wasn't the best word choice, but I'm guessing it's reflective of social use. I don't know what else a layman might call "not enunciating", especially since there are several factors involved such as the examples above.
The rest of your comment, as well as chasing's comment, seem to be hinged on the idea that there's only one definition of mumbling, which I just don't agree with, but I won't continue to argue against it either. If you have a better title for the article, I would direct it to the writer.
> You’re also more likely to [phonetically] reduce words
> if they’re predictable in the context, so that the word
> fine would be pronounced less distinctly in a sentence
> like “You’re going to be just fine” than “The last word
> in this sentence is fine.”
If pronouncing words less distinctly isn't mumbling, what is it?It's mumbling if the listener doesn't understand the meaning of the word or words at all. Which might be data compression, but I don't think of mumbles a being any more concise, just less intelligible.
> ...the word fine would be pronounced less distinctly in a sentence like “You’re going to > be just fine” than “The last word in this sentence is fine.”
This is again, just semantics, but I suppose you can say it's something akin to "concatenating" or "slurring," although the latter has its own connotations.
> Although in elementary school we learned to call them
> "contractions.
This is the part of your understanding that is incorrect. You're talking about contractions, which linguists call Synaeresis [1]. The article talks about Vowel (Phonetic) Reductions [2], which are changes in the sounds that the speaker emits, not the complete removal of the sounds.[1] http://en.wikipedia.org/wiki/Synaeresis [2] http://en.wikipedia.org/wiki/Vowel_reduction
That phrase is a gem
I won't argue that calling it 'data compression' is nothing more than cute spin, though.
And on the point of switching between languages constantly, I've noticed myself loosing a bit of my pronunciation and vocabulary of my native tongue. I blame it on living and working abroad for 8+ years. Makes sense I guess, but still annoying to myself...
I'm glad the article recognises this (and the example immediately following the quote is instructive). It's a natural habit to do this kind of 'data-compression' when you're working with the same people all the time but this is also the reason that communication is difficult across different groups and cultures. It requires you to make an effort to listen and check your own assumptions if you want to actually communicate effectively, rather than talking past each other (or worse, walking away with different ideas about what was decided).
Eh, this can also denote synergistic group think or collective creativity. Expect the unexpected, but within a clearly defined range of variability. I'm not talking specifically about software development btw; consider the surrealists or any other artistic or philosophical movement (or literature, music, mathematics etc). People have ideas together, walk away, and then have mental independence. Mental independence is good, because too much binding in thought = paranoia, nervous, control obsessed people. Too little and it seems like people don't care. It's a balance.
I think you've missed my point. I was mostly referring to things like meetings, where people typically are trying to reach an agreement (or decision) about something. If those people are from different cultures, then a mismatch can arise where people think they're talking about the same thing but only realise later that things have gone wrong. Even then, people tend towards recriminations, rather than root-causing and realising that their terms mean different things. Take the example from the end of the post itself (where 'skiing' meant different things to both people -- if they hadn't clarified, they'd have parted with vastly different views on what was discussed).
So instead, you have to build and discard internal explanatory models of my meaning, criticizing them by cross-checking them with other things I've said, and with your understanding of my understanding of the world. Meanwhile, I'm doing the same thing on the other side, hypothesizing the models that you're creating based on what I've said and trying to add more words to fill any gaps in what I presume that you're presuming that I mean.
When we arrive at a point where you and I both believe that you hold a consistent mental model of what I wished to convey, then we believe that I have communicated to you.
Stated that way, it's clear that communication is really, really hard -- even though we do all of that model building and evaluation without conscious effort in most cases. And it's also quite obvious why it's easier to communicate with people you know well, because both sides have a better mental model of the other's mental model. Both are _wrong_, always, but they're less wrong than similar situations between people with less shared context.
This view also makes it abundantly clear that it's important to validate communication. If you restate to me in your own words what you believe I intended to convey, there's a good chance I'll catch any major discrepancies between what I intended and what you got. A good chance, but we can still end up believing that we're in agreement when we're not.
In theory it is possible to define a language and communication techniques that do not depend on this iterative, contextualized method. This is essentially what we do in formal languages, such as those we use in mathematics or programming. But it is not how people communicate because it's actually far more efficient to rely on compression via shared context than it is to communicate with formal precision. Further, formal communication only obviates guesswork and criticism at the level of understanding which is directly expressed. I can read an assembler program and understand with perfect precision what the individual instructions do, but the leap to understanding the goal of the program again requires guesswork and criticism.
As an aside, it's interesting to note that the process of guess-and-evaluate is essentially the same as the scientific method of hypothesize-and-test and even the same as the evolutionary method of vary-and-select. There's a compelling argument that all knowledge creation occurs via this process -- and communication is knowledge creation, even if it simply conveys an idea from one brain to another, because there's no direct transfer mechanism the receiver of the idea must create it based on observations of the words of the giver.
I feel like science and mathematics (and even computer science) attempts to counter this.
If we can mechanically generate mathematical proofs, and those proofs can be proven equivalent to one another, then we have essentially simplified the abstraction mechanics of the individual brain and transferred them to a computer.
I view abstraction as a means for expanding all potential permutations of a given model and it's application, and then a reduction to a different set of terms that connects models.
We might be able to prove that we can agree with one another, but we might not be able to prove that we agree with our own selves. We can always make the problem more difficult individually by guessing and creating more questions.
To me the process is two sides of the same coin. One side is creation, the other side is destruction. You can't convey an idea without having an idea, and you can't question that idea without having another idea. Negation is still a logical mechanism. You can question whether there is more to think about than a choice between [(exist) or (does not exist)].
I really prefer to think about possibility and potential. It's an open space to me.
This can be an assumption about the meaning of a word or subtleties in the collection of concepts that connect to that word (as often seems to be the case with most computer science and mathematics material on the internet). Engineering interestingly enough does not seem to suffer from this insanity.
This can happen from overgeneralizing and even correct simplification. The pattern still fits, but both people have applied the pattern to different 'other stuff'.
We both have different points, so we both are directing this dialogue towards unrelated directions. I will attempt to connect them. I agree with you. Meaning can be an issue in communication. Form can be an issue in communication as well.
The schwa sound is a slight uh. So America is pronounced uhMERIKuh, sounds like MERIK, then they link lots of words, so instead of BUS STOP, you will hear BUSTOP. Or instead of "I am going", You will hear, "I'm going", but the I will be compressed to an uh and liked to the m with a y sound. Iyam, "yuhM going"
Chances are that's what your cousin was doing but on a less subtle level.
For example, you could probably interpret "thuh kwuhck bruhn fuhx juhmps uhvr thuh luhzy dug" quite readily, but not "duh dwid drowd dod dudd oded duh dudy dod".
It is true that vowels are sometimes the distinguishing phoneme between minimal pairs, but the reality is that we are quite adept at calibrating ourselves to cope with vowel variation.
One example is actually head size, of all things. I won't go into all the psychoacoustics involved (not my area of expertise), but your brain adjusts its expectations for how a given vowel should sound based on the speaker's unique "instrumental" qualities. In other words, you can end up with two very objectively different waveforms that your brain is able to match up without hesitation.
A more familiar example is dialects. A Southern American speaker might say "ice", and to a General American speaker, it may sound much more like "ass", but this kind of variation doesn't really lead to the hilarious confusion one might expect. After a quick "scan" of another dialect, we usually adapt fairly quickly, and we retain those "settings" for the next time we hear a similar dialect.
One example that's not so easy to work around might be the pen-pin merger. In general, it leads to few mix-ups. But those speakers, "pen" and "pin" are homophones, and unlike other such pairs (bin-Ben, lint-lent, mint-meant, tin[t]-ten[t], win-when, etc.) they may not be easily differentiable by context. In response, many speakers refer to pens as "ink pens" and pins as "stick pins", which avoids the ambiguity (animal pens and female swans aren't really an issue I suppose).
So even when vowels lead to genuine ambiguity, we get around it pretty easily.
"Be conservative in what you do, be liberal in what you accept from others."
You can save yourself a headache if you communicate as clearly and accurately as possible. At work, with friends, with a partner. I don't care what mumbling is a sign of, I care about its result. Don't optimize the wrong thing. Just like nobody likes seeing ugly JPEG artifacts, nobody likes to recognize mumbling.
Also,
"Why do native speakers of the language you’re studying talk too fast for you to understand them? Because otherwise, they could talk faster and still understand each other."
http://watergate.info/1972/06/23/the-smoking-gun-tape.html
>Haldeman: .../only way to solve this, and we’re set up beautifully to do it, ah, in that and that…the only network that paid any attention to it last night was NBC…they did a massive story on the Cuban…
>Nixon: That’s right.
>Haldeman: thing.
>Nixon: Right.
>Haldeman: That the way to handle this now is for us to have Walters call Pat Gray and just say, “Stay the hell out of this…this is ah, business here we don’t want you to go any further on it.” That’s not an unusual development,…
>Nixon: Um huh.
>Haldeman: …and, uh, that would take care of it.
>Nixon: What about Pat Gray, ah, you mean he doesn’t want to?
Definitely not about compression, though.
In my opinion, it gives a satisfying explanation as to why many languages (about half of them) divide their words in noun categories or genders, which are rarely sex-based. It's a system of redundancy, which allows for noisy or compressed speech (either mumbled, or at a party, or fast spoken), to still be understood, because the gender endings give clues to what the original word was
It seems like the author is arguing that in order to be lazy about sound production, you need to expend energy picking out which sounds you need and which can be safely left out. That's all well and good, but in the middle of the article, the author herself refers to mumbling as a kind of "strategic laziness"!
Curse these headlines!
My son does mumble at times but I've always thought it was when he was saying something he knew he wasn't supposed to.
I'm German and I really wasn't aware of this association at all. I associate mumbling with shyness … and that's about it. And what's more that association to laziness seems positively weird and non-sensical to me.
And forget about southerners who speak English as if it were French. Eass for east. Repore for report. Assed for asked, etc. (really you 'assed' me a question?) It can quickly make a conversation ambiguous as this tendency results in lots oh homonyms.
Best way to make sure father-in-law speaks up is to have my father around.
Downside is it physically wears my father-in-law out. He just can't handle expending that much effort into speaking.
Ok, off my soapbox.