<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Plain English</title>
	<atom:link href="http://bocktherobber.com/2008/02/plain-english/feed" rel="self" type="application/rss+xml" />
	<link>http://bocktherobber.com/2008/02/plain-english</link>
	<description>Offending everybody since 2006</description>
	<pubDate>Fri, 05 Sep 2008 16:01:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Andrew</title>
		<link>http://bocktherobber.com/2008/02/plain-english#comment-14749</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Sat, 23 Feb 2008 12:46:02 +0000</pubDate>
		<guid isPermaLink="false">http://bocktherobber.com/2008/02/plain-english#comment-14749</guid>
		<description>... and moving forward (or is it backward?), I have no objection/problem/issue at all to the use of the word "issue/issues" being used to describe a Weblog on Google, not even when the particular Weblog has issues with the word "issues". 

Gesundheit!</description>
		<content:encoded><![CDATA[<p>&#8230; and moving forward (or is it backward?), I have no objection/problem/issue at all to the use of the word &#8220;issue/issues&#8221; being used to describe a Weblog on Google, not even when the particular Weblog has issues with the word &#8220;issues&#8221;. </p>
<p>Gesundheit!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bock</title>
		<link>http://bocktherobber.com/2008/02/plain-english#comment-14720</link>
		<dc:creator>Bock</dc:creator>
		<pubDate>Fri, 22 Feb 2008 23:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://bocktherobber.com/2008/02/plain-english#comment-14720</guid>
		<description>To be completely Californian about this, I'd say you meant "prioritize", not "prioritise".</description>
		<content:encoded><![CDATA[<p>To be completely Californian about this, I&#8217;d say you meant &#8220;prioritize&#8221;, not &#8220;prioritise&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Collywobbles</title>
		<link>http://bocktherobber.com/2008/02/plain-english#comment-14717</link>
		<dc:creator>Collywobbles</dc:creator>
		<pubDate>Fri, 22 Feb 2008 23:02:21 +0000</pubDate>
		<guid isPermaLink="false">http://bocktherobber.com/2008/02/plain-english#comment-14717</guid>
		<description>The term 'problem' is taboo in the IT/systems racket these days because we live in world of business 'coaches' and 'mentors' and self help gurus who tell us to 'think positive'. Plus, we are a bit spoiled and lazy. Hence, there are no problems (which imply something wrong), only "issues" (which are simply matters of perception, to be looked at in a much lighter vein, and possibly ignored, made fun of, or debated without any conclusion at 'team meetings').  This gives managers, and the people who work for them (for very nice wages and benefits) great encouragement:  Rather than fix the problem, they'll argue that your perception of it is simply wrong, will 'prioritise' it at the bottom of their 'task lists', and, take off on holidays. Meanwhile, you're stuck with a system that doesn't work properly and no way to get your money back, unless you can afford a lot of legal advice. 

And then some Polish or Indian guy who actually wants to fix the problem, and for half price, gets the job instead and we're all fucked. Then we really do have an issue...</description>
		<content:encoded><![CDATA[<p>The term &#8216;problem&#8217; is taboo in the IT/systems racket these days because we live in world of business &#8216;coaches&#8217; and &#8216;mentors&#8217; and self help gurus who tell us to &#8216;think positive&#8217;. Plus, we are a bit spoiled and lazy. Hence, there are no problems (which imply something wrong), only &#8220;issues&#8221; (which are simply matters of perception, to be looked at in a much lighter vein, and possibly ignored, made fun of, or debated without any conclusion at &#8216;team meetings&#8217;).  This gives managers, and the people who work for them (for very nice wages and benefits) great encouragement:  Rather than fix the problem, they&#8217;ll argue that your perception of it is simply wrong, will &#8216;prioritise&#8217; it at the bottom of their &#8216;task lists&#8217;, and, take off on holidays. Meanwhile, you&#8217;re stuck with a system that doesn&#8217;t work properly and no way to get your money back, unless you can afford a lot of legal advice. </p>
<p>And then some Polish or Indian guy who actually wants to fix the problem, and for half price, gets the job instead and we&#8217;re all fucked. Then we really do have an issue&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bock</title>
		<link>http://bocktherobber.com/2008/02/plain-english#comment-14685</link>
		<dc:creator>Bock</dc:creator>
		<pubDate>Fri, 22 Feb 2008 14:12:04 +0000</pubDate>
		<guid isPermaLink="false">http://bocktherobber.com/2008/02/plain-english#comment-14685</guid>
		<description>And your objection to that is ...?</description>
		<content:encoded><![CDATA[<p>And your objection to that is &#8230;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://bocktherobber.com/2008/02/plain-english#comment-14671</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 22 Feb 2008 12:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://bocktherobber.com/2008/02/plain-english#comment-14671</guid>
		<description>In Google a web search using:&#62;  "bock the robber" brings this up:

Bock The Robber    · Weblogs
Irish-based site, commenting on world issues, current affairs, politics, music, religion, sport, corruption and government incompetence. With stories.

.... world issues !!!!</description>
		<content:encoded><![CDATA[<p>In Google a web search using:&gt;  &#8220;bock the robber&#8221; brings this up:</p>
<p>Bock The Robber    · Weblogs<br />
Irish-based site, commenting on world issues, current affairs, politics, music, religion, sport, corruption and government incompetence. With stories.</p>
<p>&#8230;. world issues !!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bock</title>
		<link>http://bocktherobber.com/2008/02/plain-english#comment-14614</link>
		<dc:creator>Bock</dc:creator>
		<pubDate>Thu, 21 Feb 2008 18:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://bocktherobber.com/2008/02/plain-english#comment-14614</guid>
		<description>Can't argue with that, John.  I have no objection to jargon as long as it doesn't escape to breed in the wild.</description>
		<content:encoded><![CDATA[<p>Can&#8217;t argue with that, John.  I have no objection to jargon as long as it doesn&#8217;t escape to breed in the wild.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Mc</title>
		<link>http://bocktherobber.com/2008/02/plain-english#comment-14613</link>
		<dc:creator>John Mc</dc:creator>
		<pubDate>Thu, 21 Feb 2008 18:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://bocktherobber.com/2008/02/plain-english#comment-14613</guid>
		<description>Given that I work in IT, and am interested in language, this is something I have actually thought about. Actually "issues" is probably more precise than the black and white but vague definition "problems". A problem implies that something is wrong, and that it is specific. Something like " the server is down" can  have a plethora of causes" in fact 9 times out of 10, servers are not really down, it is something else, network, (router, firewall etc), software, (application server, web servers,  etc). Therefore initially to describe something as an issue is probably correct until further diagnosis points to something more specific.
You wouldn't want to go to the doctor with a vague chest pain and have him / her immediately decide that you had heart problems, and operate,  when  n reality you had indigestion.
My experience in the IT world is that the most dangerous people are those that see IT as a black and white universe and make specific and hurried diagnosis. Language is very important here. Especially as to the lay person IT is a catch-all term. To overuse my Doctors analysis, it's kind of like saying The Medical Profession to cover Doctors only, when it really covers, nurses, EMT's, etc. IT people come from many different arenas and need a common language, it needs to be precise, I agree there, but more importantly it needs to be accurate, even if this creates vagueness initially. It’s the age old problem that the words a professional uses to communicate to another professional ultimately come across as bullshit to the lay person. OK, I need to stop now, before I disappear up my own arse.</description>
		<content:encoded><![CDATA[<p>Given that I work in IT, and am interested in language, this is something I have actually thought about. Actually &#8220;issues&#8221; is probably more precise than the black and white but vague definition &#8220;problems&#8221;. A problem implies that something is wrong, and that it is specific. Something like &#8221; the server is down&#8221; can  have a plethora of causes&#8221; in fact 9 times out of 10, servers are not really down, it is something else, network, (router, firewall etc), software, (application server, web servers,  etc). Therefore initially to describe something as an issue is probably correct until further diagnosis points to something more specific.<br />
You wouldn&#8217;t want to go to the doctor with a vague chest pain and have him / her immediately decide that you had heart problems, and operate,  when  n reality you had indigestion.<br />
My experience in the IT world is that the most dangerous people are those that see IT as a black and white universe and make specific and hurried diagnosis. Language is very important here. Especially as to the lay person IT is a catch-all term. To overuse my Doctors analysis, it&#8217;s kind of like saying The Medical Profession to cover Doctors only, when it really covers, nurses, EMT&#8217;s, etc. IT people come from many different arenas and need a common language, it needs to be precise, I agree there, but more importantly it needs to be accurate, even if this creates vagueness initially. It’s the age old problem that the words a professional uses to communicate to another professional ultimately come across as bullshit to the lay person. OK, I need to stop now, before I disappear up my own arse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Red Mist</title>
		<link>http://bocktherobber.com/2008/02/plain-english#comment-14602</link>
		<dc:creator>Red Mist</dc:creator>
		<pubDate>Thu, 21 Feb 2008 14:31:03 +0000</pubDate>
		<guid isPermaLink="false">http://bocktherobber.com/2008/02/plain-english#comment-14602</guid>
		<description>Yesterday I was at a Seminar (meeting) and counted 8 "going forwards" instead of "in future" and a few "at this point in times", making a surprsing come back in usage, before my brain numbed and even though I was present at the meeting, I was in fact enjoying a stroll around the Burren in my head.  A rocky place my head and a store of imaginative escape. I wish all these guys could take their, CDP points, Cdps and Ops incorporating the PMDS, Tms and Pdps, not forgetting RM plans and H&#38;S "issues" and stick them up their arse.</description>
		<content:encoded><![CDATA[<p>Yesterday I was at a Seminar (meeting) and counted 8 &#8220;going forwards&#8221; instead of &#8220;in future&#8221; and a few &#8220;at this point in times&#8221;, making a surprsing come back in usage, before my brain numbed and even though I was present at the meeting, I was in fact enjoying a stroll around the Burren in my head.  A rocky place my head and a store of imaginative escape. I wish all these guys could take their, CDP points, Cdps and Ops incorporating the PMDS, Tms and Pdps, not forgetting RM plans and H&amp;S &#8220;issues&#8221; and stick them up their arse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sniffle&#38;Cry</title>
		<link>http://bocktherobber.com/2008/02/plain-english#comment-14598</link>
		<dc:creator>Sniffle&#38;Cry</dc:creator>
		<pubDate>Thu, 21 Feb 2008 13:16:05 +0000</pubDate>
		<guid isPermaLink="false">http://bocktherobber.com/2008/02/plain-english#comment-14598</guid>
		<description>Ah fucking face it Bock, you’re getting old! That’s the ambiguous way young folk talk these days. Have you seen teenage text-speak, your issue-problem dilemma is very much in the cheap seats, u c, do u c? And remember what happened the last time you did text; it’s an omen, your scaldy shinnedness.</description>
		<content:encoded><![CDATA[<p>Ah fucking face it Bock, you’re getting old! That’s the ambiguous way young folk talk these days. Have you seen teenage text-speak, your issue-problem dilemma is very much in the cheap seats, u c, do u c? And remember what happened the last time you did text; it’s an omen, your scaldy shinnedness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Conan Drumm</title>
		<link>http://bocktherobber.com/2008/02/plain-english#comment-14597</link>
		<dc:creator>Conan Drumm</dc:creator>
		<pubDate>Thu, 21 Feb 2008 12:30:45 +0000</pubDate>
		<guid isPermaLink="false">http://bocktherobber.com/2008/02/plain-english#comment-14597</guid>
		<description>It's spin.

If you've an issue with that, ok. No problem. 

It's a subtle excercise in the re-location of fault responsibilty. It goes from something created by the 'service provider' (that they have to do something about) to something the consumer experiences (and has to do something about).</description>
		<content:encoded><![CDATA[<p>It&#8217;s spin.</p>
<p>If you&#8217;ve an issue with that, ok. No problem. </p>
<p>It&#8217;s a subtle excercise in the re-location of fault responsibilty. It goes from something created by the &#8217;service provider&#8217; (that they have to do something about) to something the consumer experiences (and has to do something about).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
