<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments for STS Blog</title>
	<link>http://blog.shoap.com</link>
	<description>Shoap Technical Services on technical writing, business, and technology</description>
	<pubDate>Fri, 05 Sep 2008 14:39:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>Comment on In Defense of Jargon by Shaun</title>
		<link>http://blog.shoap.com/2007/12/06/in-defense-of-jargon/#comment-68</link>
		<dc:creator>Shaun</dc:creator>
		<pubDate>Wed, 04 Jun 2008 18:37:20 +0000</pubDate>
		<guid>http://blog.shoap.com/2007/12/06/in-defense-of-jargon/#comment-68</guid>
		<description>Steve, thanks for the great comment. You're right that my example phrase could actually be meaningful to some people, but that doesn't make it more valuable. "Leveraging synergistic best practices" doesn't pack any extra meaning into the phrases because it doesn't pack in any specifics. You could rephrase it in plain English to a much stronger effect without bumping up your word count much. In fact, your plain English example was far more powerful. The whole purpose of using a phrase like that is at best to be isolating, at worst to obfuscate the writer's ignorance.

On the other hand, if we build on my technical jargon example a little bit, I could say that "We're going to convert our backend to an SOA based on RESTful APIs." And while that is also isolating to the layperson who has no clue what it means, it serves a purpose because it packs in a ton of specifics to the intended audience. The intent here is not isolate or obfuscate; the intent is efficiency of communications.

I think you hit the nail on the head when you said that rampant overuse compounds the problem. I know I turn off immediately when I hear someone say we're going to leverage anything. So, while "leveraging synergistic best practices" certainly can mean something, my question is what benefit do you get when you could easily say the same thing in plain English to better effect? I'd still contend that corporate jargon of that sort serves no real benefit except to identify the speaker as a member of the club. As you say, "When the giants speak among themselves, they often use a little jargon."</description>
		<content:encoded><![CDATA[<p>Steve, thanks for the great comment. You&#8217;re right that my example phrase could actually be meaningful to some people, but that doesn&#8217;t make it more valuable. &#8220;Leveraging synergistic best practices&#8221; doesn&#8217;t pack any extra meaning into the phrases because it doesn&#8217;t pack in any specifics. You could rephrase it in plain English to a much stronger effect without bumping up your word count much. In fact, your plain English example was far more powerful. The whole purpose of using a phrase like that is at best to be isolating, at worst to obfuscate the writer&#8217;s ignorance.</p>
<p>On the other hand, if we build on my technical jargon example a little bit, I could say that &#8220;We&#8217;re going to convert our backend to an SOA based on RESTful APIs.&#8221; And while that is also isolating to the layperson who has no clue what it means, it serves a purpose because it packs in a ton of specifics to the intended audience. The intent here is not isolate or obfuscate; the intent is efficiency of communications.</p>
<p>I think you hit the nail on the head when you said that rampant overuse compounds the problem. I know I turn off immediately when I hear someone say we&#8217;re going to leverage anything. So, while &#8220;leveraging synergistic best practices&#8221; certainly can mean something, my question is what benefit do you get when you could easily say the same thing in plain English to better effect? I&#8217;d still contend that corporate jargon of that sort serves no real benefit except to identify the speaker as a member of the club. As you say, &#8220;When the giants speak among themselves, they often use a little jargon.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on In Defense of Jargon by Strong Language</title>
		<link>http://blog.shoap.com/2007/12/06/in-defense-of-jargon/#comment-53</link>
		<dc:creator>Strong Language</dc:creator>
		<pubDate>Sat, 26 Apr 2008 13:25:18 +0000</pubDate>
		<guid>http://blog.shoap.com/2007/12/06/in-defense-of-jargon/#comment-53</guid>
		<description>I'm in full agreement . . . almost.

Your main points are exactly right. But even a phrase like “leveraging synergistic best practices going forward” can have a specific meaning to a specific audience.

For example, I write corpcom (now that's jargon!) for a Fortune 500 company recently acquired by a Global 500 company. When the giants speak between themselves, they often use a little jargon.

To simplify a complex business model, what the acquirer bought was synergies. One example is the acquired company's metalcasting expertise and capabilities, which fill a strategic gap in the acquirer's global chain.

Some of the acquired company's best practices relate to those synergies. And those will be leveraged going forward, or a few billion bucks will have been wasted.

Of course any idiot can string the words together -- Dilbert used to run a great "mission statement generator" that would do it for you -- and rampant overuse compounds the problem.

But I can see such a phrase in a C-level communication, and not just to obfuscate the writer's ignorance.

But otherwise -- well said.</description>
		<content:encoded><![CDATA[<p>I&#8217;m in full agreement . . . almost.</p>
<p>Your main points are exactly right. But even a phrase like “leveraging synergistic best practices going forward” can have a specific meaning to a specific audience.</p>
<p>For example, I write corpcom (now that&#8217;s jargon!) for a Fortune 500 company recently acquired by a Global 500 company. When the giants speak between themselves, they often use a little jargon.</p>
<p>To simplify a complex business model, what the acquirer bought was synergies. One example is the acquired company&#8217;s metalcasting expertise and capabilities, which fill a strategic gap in the acquirer&#8217;s global chain.</p>
<p>Some of the acquired company&#8217;s best practices relate to those synergies. And those will be leveraged going forward, or a few billion bucks will have been wasted.</p>
<p>Of course any idiot can string the words together &#8212; Dilbert used to run a great &#8220;mission statement generator&#8221; that would do it for you &#8212; and rampant overuse compounds the problem.</p>
<p>But I can see such a phrase in a C-level communication, and not just to obfuscate the writer&#8217;s ignorance.</p>
<p>But otherwise &#8212; well said.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on White Space in Flare Searches by Daniel Labrador</title>
		<link>http://blog.shoap.com/2008/02/20/white-space-in-flare-searches/#comment-27</link>
		<dc:creator>Daniel Labrador</dc:creator>
		<pubDate>Sat, 23 Feb 2008 16:44:17 +0000</pubDate>
		<guid>http://blog.shoap.com/2008/02/20/white-space-in-flare-searches/#comment-27</guid>
		<description>So I guess you mean "feature" as in "it's not a bug, it's a feature"...?</description>
		<content:encoded><![CDATA[<p>So I guess you mean &#8220;feature&#8221; as in &#8220;it&#8217;s not a bug, it&#8217;s a feature&#8221;&#8230;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How To: Remove Extra NBSPs from Flare by White Space in Flare Searches &#124; STS Blog</title>
		<link>http://blog.shoap.com/2007/09/04/how-to-remove-extra-nbsps-from-flare/#comment-26</link>
		<dc:creator>White Space in Flare Searches &#124; STS Blog</dc:creator>
		<pubDate>Wed, 20 Feb 2008 16:13:26 +0000</pubDate>
		<guid>http://blog.shoap.com/2007/09/04/how-to-remove-extra-nbsps-from-flare/#comment-26</guid>
		<description>[...] covered in the past some of Flare&#8217;s wonky behavior when it comes it to white space. I found another fun trick involving white space while searching in Flare 2.5 [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] covered in the past some of Flare&#8217;s wonky behavior when it comes it to white space. I found another fun trick involving white space while searching in Flare 2.5 [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Passive Voice Rescued By Internet Scientists by Jeffrey Shoap</title>
		<link>http://blog.shoap.com/2007/10/23/passive-voice-cleared-by-internet-scientists/#comment-3</link>
		<dc:creator>Jeffrey Shoap</dc:creator>
		<pubDate>Fri, 26 Oct 2007 18:21:19 +0000</pubDate>
		<guid>http://blog.shoap.com/2007/10/23/passive-voice-cleared-by-internet-scientists/#comment-3</guid>
		<description>Prepare yourself for a good flogging at the next network event.</description>
		<content:encoded><![CDATA[<p>Prepare yourself for a good flogging at the next network event.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Office 2007: Don&#8217;t Be Skeered by daniel</title>
		<link>http://blog.shoap.com/2007/08/24/office-2007-dont-be-skeered/#comment-2</link>
		<dc:creator>daniel</dc:creator>
		<pubDate>Mon, 15 Oct 2007 17:19:19 +0000</pubDate>
		<guid>http://blog.shoap.com/2007/08/24/office-2007-dont-be-skeered/#comment-2</guid>
		<description>Maybe they should've included "Don't Panic" in big friendly letters somewhere on that toolbar.</description>
		<content:encoded><![CDATA[<p>Maybe they should&#8217;ve included &#8220;Don&#8217;t Panic&#8221; in big friendly letters somewhere on that toolbar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why can&#8217;t I put my files on my new hard drive? by daniel</title>
		<link>http://blog.shoap.com/2007/10/15/why-cant-i-put-my-files-on-my-new-hard-drive/#comment-1</link>
		<dc:creator>daniel</dc:creator>
		<pubDate>Mon, 15 Oct 2007 15:59:38 +0000</pubDate>
		<guid>http://blog.shoap.com/2007/10/15/why-cant-i-put-my-files-on-my-new-hard-drive/#comment-1</guid>
		<description>Just wanted to add that we discovered that a brand-new Mac mini running a beta copy of Mac OS Leopard is able to read and write to the NTFS-formatted partitions on the drives.  I'm not sure if this is true for other versions of OS X, but I figured it would be useful to point out (since it makes the file system on the drive a non-issue).

Also, if you find that your Windows computer is unable to open a USB drive after doing partition-and-format type work on external hard drives, make sure your issue is not due to drive letter conflicts.  After struggling with the issue for a few minutes, I realized that the network drive on our client's corporate network uses the same drive letter that the machine was trying to assign to my USB key.  This is something fairly easy to fix with the Windows disk management utility, but it took me a while just to identify the problem...</description>
		<content:encoded><![CDATA[<p>Just wanted to add that we discovered that a brand-new Mac mini running a beta copy of Mac OS Leopard is able to read and write to the NTFS-formatted partitions on the drives.  I&#8217;m not sure if this is true for other versions of OS X, but I figured it would be useful to point out (since it makes the file system on the drive a non-issue).</p>
<p>Also, if you find that your Windows computer is unable to open a USB drive after doing partition-and-format type work on external hard drives, make sure your issue is not due to drive letter conflicts.  After struggling with the issue for a few minutes, I realized that the network drive on our client&#8217;s corporate network uses the same drive letter that the machine was trying to assign to my USB key.  This is something fairly easy to fix with the Windows disk management utility, but it took me a while just to identify the problem&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
