# Language amusements, corporate and academic division

**URL:** <https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804>\
**Category:** Miscellaneous and Personal Stuff I Must Share\
**Created:** [May 27, 2016, 1:01pm UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804 "2016-05-27T13:01:33Z")\
**Posts on this page:** 11\
**Page:** 3

<div class="post-metadata">

**Author:** ![robert\_columbia](https://avatars.discourse-cdn.com/v4/letter/r/e79b87/32.png) [@robert\_columbia](https://boards.straightdope.com/u/robert_columbia)\
**Post date:** [June 4, 2016, 12:17am UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/41 "2016-06-04T00:17:47Z")

</div>

> [@Chronos](#):
>
> The problem isn’t in people using jargon instead of communicating clearly. The problem is when people fail to realize that communicating clearly is the purpose of jargon. It’s not meant to be a shibboleth.
> 
> Take “velocity”, for instance. Physicists have two different words for “speed” and “velocity” because they mean two subtly different things, and the distinction is often important. It happens that “velocity” is more often the concept of interest to a physicist, so people think that “velocity” sounds more sciencey. And so we see laymen (or sloppy physicists) referring to things like “escape velocity”. Except that that should actually be “escape speed”. “Speed”, in this case, is the correct use of the jargon, even though it doesn’t sound as impressive…

There are plenty of additional examples:

In Unix and many Unixlike operating systems, “terminating” a process and “killing” a process are two different things. When you terminate a process, you give it a chance to close down and perform any necessary cleanup such as releasing file handles and saving state data. When you kill a process, it is immediately stopped without mercy, leaving any unsaved data unsaved.

In law, “larceny” is a specific common-law crime that has been discussed and analyzed hundreds of ways in the past several hundred years. It encompasses many, but not all, of the things that we commonly refer to as “stealing” or “theft”. It would be wrong for a lawyer (in most jurisdictions, at least) to use his leet legal-talking skillz to speak about committing “larceny” of Cable TV unless he is speaking about physically taking and walking off with physical cables, converters, or routers. Similarly, violating copyright, taking someone’s idea, committing cultural appropriation, or committing other acts are often considered “stealing” in a moral sense but are not larceny and would not normally fall under larceny-related statues or case law.

---

<div class="post-metadata">

**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\
**Post date:** [June 4, 2016, 12:45am UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/42 "2016-06-04T00:45:51Z")

</div>

> [@Ulf\_the\_Unwashed](#):
>
> I’m currently doing some freelance work for a large publisher. I just received an email inviting me to attend a “concepting meeting.”
> 
> Yesterday there was another email urging us to “surface any concerns or comments.”
> 
> English is really quite wonderful, isn’t it?

This is a wonderful thread! I think everyone who has been involved [in this one](http://boards.straightdope.com/sdmb/showthread.php?t=794153), especially the self-identified descriptivists, must absolutely read it!

> [@pullin](#):
>
> And last year some executive discovered the word “Aperture”. It actually does mean an opening and they’ve been parroting it to one another endlessly. (“Do you have aperture for this project, Jim? Can you provide bandwidth?”)
> 
> In the end-of-year address, one of the upper execs accidentally got it right when she admonished we should “…open our minds and our apertures to the company to ensure long term success.”

Priceless! And when they’ve opened their apertures, they can stick their language abuses right up them!

> [@Mean\_Mr.Mustard](#):
>
> **Drill down**.  
> …  
> “Once a problem is identified, reach out to the proper department so they can drill down to find the best approach to solve it”.

Drill down and surface a solution.

> [@Chronos](#):
>
> The problem isn’t in people using jargon instead of communicating clearly. The problem is when people fail to realize that communicating clearly is the purpose of jargon. It’s not meant to be a shibboleth.
> 
> Take “velocity”, for instance. Physicists have two different words for “speed” and “velocity” because they mean two subtly different things, and the distinction is often important. It happens that “velocity” is more often the concept of interest to a physicist, so people think that “velocity” sounds more sciencey. And so we see laymen (or sloppy physicists) referring to things like “escape velocity”. Except that that should actually be “escape speed”. “Speed”, in this case, is the correct use of the jargon, even though it doesn’t sound as impressive …

Exactly my point in the other thread I noted – when people use words in ways that are incorrect, it impedes communication, plain and simple. The fact that in some distant future so many people may (or may not) be repeating the same mistake that it becomes entrenched usage doesn’t change that fact.

Although I don’t really think that “velocity” is wrong in “escape velocity”. Escape velocity is a vector whose direction is away from the planet. If you’re moving at “escape speed” towards the ground you’re not going to go anywhere. You’re going to end up “drilling down”!

> [@PatrickLondon](#):
>
> Once I saw a memo stressing the importance of making sure all the relevant stakeholders were “in the loop, going forward”. It wasn’t my place to ask if they’d done a proper health and safety assessment…

They were in the loop going forward nicely, but then the loop got caught in all the stakes the stakeholders were carrying and it got all tangled up, and now they have to go backward to try to surface a deknotting solution, and they’d better do it quick because the drillers are coming tomorrow to drill for new paradigms.

---

<div class="post-metadata">

**Author:** ![robert\_columbia](https://avatars.discourse-cdn.com/v4/letter/r/e79b87/32.png) [@robert\_columbia](https://boards.straightdope.com/u/robert_columbia)\
**Post date:** [June 4, 2016, 1:07am UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/43 "2016-06-04T01:07:01Z")

</div>

> [@wolfpup](#):
>
> > [@PatrickLondon](#):
> >
> > …Once I saw a memo stressing the importance of making sure all the relevant stakeholders were “in the loop, going forward”. It wasn’t my place to ask if they’d done a proper health and safety assessment…
> 
> They were in the loop going forward nicely, but then the loop got caught in all the stakes the stakeholders were carrying and it got all tangled up, and now they have to go backward to try to surface a deknotting solution, and they’d better do it quick because the drillers are coming tomorrow to drill for new paradigms.

In a nutshell, they spent so much time verifying and validating that the mountain was scalable that they were unable to touch base with the team that had the ballpark figures. At the end of the day, it was too dark to see even the low hanging fruit, so everyone ended up eating their own dogfood while pushing the envelope toward a local farmer who may be able to reach out with some best practices on organic growth. They agreed to support the farmer with respect to his core competencies in cat herding if he would spin up our helicopter into the cloud so it wouldn’t impact our brick-and-mortar business.

---

<div class="post-metadata">

**Author:** ![Senegoid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/senegoid/32/6606_2.png) [@Senegoid](https://boards.straightdope.com/u/Senegoid)\
**Post date:** [June 4, 2016, 2:13am UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/44 "2016-06-04T02:13:50Z")

</div>

> [@digs](#):
>
> I can’t wait to try this!
> 
> The only problem is, I sit down front, on a raised altar, facing the congregation… and next Sunday, cracking up… (Damn you to hellllll!)

I was almost there once. On the day of my Bar Mitzvah, lo! these many years ago, I was sitting on the bimah (altar) facing everybody, and there . . .

there . . .

there was by Best Friend Since Second Grade sitting there in the second row making faces at me.

---

<div class="post-metadata">

**Author:** ![Riemann](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/riemann/32/3133_2.png) [@Riemann](https://boards.straightdope.com/u/Riemann)\
**Post date:** [June 4, 2016, 6:34am UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/45 "2016-06-04T06:34:12Z")

</div>

> [@wolfpup](#):
>
> This is a wonderful thread! I think everyone who has been involved [in this one](http://boards.straightdope.com/sdmb/showthread.php?t=794153), especially the self-identified descriptivists, must absolutely read it!..
> 
> Exactly my point in the other thread I noted – when people use words in ways that are incorrect, it impedes communication, plain and simple.

In the other thread, you failed to support your assertion that the use of _literally_ as an intensifier is any more ambiguous than the analogous metaphorical use of _incredibly_, _really_, _truly_, or _in fact_. You showed no humility or respect for evidence. Following the prescriptivist archetype, you misrepresented your arbitrary stylistic opinion as objective fact, and described speakers who use the expression as stupid and ignorant.

It does not logically follow that you are a heroic advocate of linguistic accuracy, clarity or elegance. And, despite clear explanations of what descriptivist linguistics really is, you continue to willfully misrepresent it as linguistic anarchy, where any string of words is as good as any other.

[/hijack]

Please continue. I fully endorse this mocking of incoherent corporate jargon.

---

<div class="post-metadata">

**Author:** ![glee](https://avatars.discourse-cdn.com/v4/letter/g/b5a626/32.png) [@glee](https://boards.straightdope.com/u/glee)\
**Post date:** [June 4, 2016, 9:36am UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/46 "2016-06-04T09:36:07Z")

</div>

> [@Chronos](#):
>
> The problem isn’t in people using jargon instead of communicating clearly. The problem is when people fail to realize that communicating clearly is the purpose of jargon. It’s not meant to be a shibboleth.
> 
> Take “velocity”, for instance. Physicists have two different words for “speed” and “velocity” because they mean two subtly different things, and the distinction is often important. It happens that “velocity” is more often the concept of interest to a physicist, so people think that “velocity” sounds more sciencey. And so we see laymen (or sloppy physicists) referring to things like “escape velocity”. Except that that should actually be “escape speed”. “Speed”, in this case, is the correct use of the jargon, even though it doesn’t sound as impressive.

(I struggle with physics, so excuse me if I’m wrong…)  
Velocity means speed plus direction, correct?  
A spaceship trying to travel into space needs to be facing away from the Earth - would that mean ‘escape velocity’ was correct?

---

<div class="post-metadata">

**Author:** ![Riemann](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/riemann/32/3133_2.png) [@Riemann](https://boards.straightdope.com/u/Riemann)\
**Post date:** [June 4, 2016, 9:54am UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/47 "2016-06-04T09:54:56Z")

</div>

> [@Chronos](#):
>
> It happens that “velocity” is more often the concept of interest to a physicist, so people think that “velocity” sounds more sciencey. And so we see laymen (or sloppy physicists) referring to things like “escape velocity”. Except that that should actually be “escape speed”. “Speed”, in this case, is the correct use of the jargon, even though it doesn’t sound as impressive.

There’s a corollary to this with numbers. There is an almost universal trope on tv and film that super-smart science types will state numbers to a ridiculously inappropriate number of significant figures.

Spock to Kirk: “Captain, I calculate a 41.327% probability of surviving the next attack from the alien weapon that we have just encountered for the first time and know almost nothing about.”

In reality, scientists pay constant attention to the quantity and nature of the uncertainty in their data and the limitations and approximations in their models. Only those without scientific training will mindlessly read off all the decimal places from the result of a calculation.

---

<div class="post-metadata">

**Author:** ![Ulf\_the\_Unwashed](https://avatars.discourse-cdn.com/v4/letter/u/b4bc9f/32.png) [@Ulf\_the\_Unwashed](https://boards.straightdope.com/u/Ulf_the_Unwashed)\
**Post date:** [June 4, 2016, 5:27pm UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/48 "2016-06-04T17:27:06Z")

</div>

> [@JKellyMap](#):
>
> Ulf, have you seen the current [New Yorker piece on Frog and Toad](http://www.newyorker.com/books/page-turner/frog-and-toad-an-amphibious-celebration-of-same-sex-love)? It’s sweet and wistful. I had no idea that the writer was an early AIDS sufferer.
> 
> P.S. Thanks for the explanation. Now I see why, in my world, “story maps” have become a thing lately.
> 
> ETA: Your parody is hilarious!

Glad you liked it! Thanks for the “suggestion.” I used Frog and Toad frequently when I was teaching early elementary grades, as well as when my own kids were learning to read, and have a real soft spot for the books.

Thanks very much for the link to the New Yorker article on Lobel. “Sweet and wistful” is exactly right. I sent the link on to my son, now grown, but as mentioned a Lobel fan from way back.

---

<div class="post-metadata">

**Author:** ![JKellyMap](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/jkellymap/32/15880_2.png) [@JKellyMap](https://boards.straightdope.com/u/JKellyMap)\
**Post date:** [June 4, 2016, 10:39pm UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/49 "2016-06-04T22:39:25Z")

</div>

🙂

---

<div class="post-metadata">

**Author:** ![movingfinger](https://avatars.discourse-cdn.com/v4/letter/m/7ab992/32.png) [@movingfinger](https://boards.straightdope.com/u/movingfinger)\
**Post date:** [June 5, 2016, 5:33am UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/50 "2016-06-05T05:33:28Z")

</div>

“Drill down”? Actually, I kind of like that one as it will soon be replaced by “Utilize a soils displacement instrument in a sub-surface orientation.”

---

<div class="post-metadata">

**Author:** ![Senegoid](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/senegoid/32/6606_2.png) [@Senegoid](https://boards.straightdope.com/u/Senegoid)\
**Post date:** [June 5, 2016, 6:16am UTC](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804/51 "2016-06-05T06:16:26Z")

</div>

> [@Riemann](#):
>
> There’s a corollary to this with numbers. There is an almost universal trope on tv and film that super-smart science types will state numbers to a ridiculously inappropriate number of significant figures.
> 
> Spock to Kirk: “Captain, I calculate a 41.327% probability of surviving the next attack from the alien weapon that we have just encountered for the first time and know almost nothing about.”
> 
> In reality, scientists pay constant attention to the quantity and nature of the uncertainty in their data and the limitations and approximations in their models. Only those without scientific training will mindlessly read off all the decimal places from the result of a calculation.

I had an assistant-division-leader (basically, boss’s boss’s #2 guy) who did all our annual evaluations like this. He had the shift supervisors fill out a questionnaire for each person on their shifts, evaluating us on a scale of 1 to 5 (whole numbers only) on several attributes. Then the computed the average of each employee’s scores on those scales, which he kept to two or three decimal places. He used these results to rank all the employees in order, which had the potential to create various anomalies. I explained this to him once, but I didn’t get the sense that he understood.

[Previous page](https://boards.straightdope.com/t/language-amusements-corporate-and-academic-division/755804.md?page=2)
