<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: IT People</title>
	<atom:link href="http://edge4dev.wordpress.com/2007/11/29/it-people/feed/" rel="self" type="application/rss+xml" />
	<link>http://edge4dev.wordpress.com/2007/11/29/it-people/</link>
	<description>Defining electronic collaboration for development sector</description>
	<lastBuildDate>Thu, 31 Jul 2008 10:58:02 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Damir Simunic</title>
		<link>http://edge4dev.wordpress.com/2007/11/29/it-people/#comment-77</link>
		<dc:creator>Damir Simunic</dc:creator>
		<pubDate>Sun, 02 Dec 2007 18:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://edge4dev.wordpress.com/2007/11/29/it-people/#comment-77</guid>
		<description>Tim, agreed: probably it won&#039;t end like the architect&#039;s profession. Because in this case there&#039;s really no profession to talk about.

I guess today&#039;s popular trends, &#039;Web 2.0&#039; and &#039;Enterprise 2.0&#039; are all about people slowly realizing there&#039;s much more to software than constant &#039;no can do&#039; excuses and bureaucracy of IT departments.

Even the infrastructure maintenance role they provide to the organization is becoming less important with advances in hardware. I envision 10-15 years from now having IT department role merging with building maintenance. Every large company employs electricians, and in the same way it will employ IT maintainers.

Producing easy to use software requires completely different skill set than an average IT department has. It will probably take the next generation of management to realize this and make the necessary transition. Today&#039;s management is too invested into the current, central role of IT department.</description>
		<content:encoded><![CDATA[<p>Tim, agreed: probably it won&#8217;t end like the architect&#8217;s profession. Because in this case there&#8217;s really no profession to talk about.</p>
<p>I guess today&#8217;s popular trends, &#8216;Web 2.0&#8242; and &#8216;Enterprise 2.0&#8242; are all about people slowly realizing there&#8217;s much more to software than constant &#8216;no can do&#8217; excuses and bureaucracy of IT departments.</p>
<p>Even the infrastructure maintenance role they provide to the organization is becoming less important with advances in hardware. I envision 10-15 years from now having IT department role merging with building maintenance. Every large company employs electricians, and in the same way it will employ IT maintainers.</p>
<p>Producing easy to use software requires completely different skill set than an average IT department has. It will probably take the next generation of management to realize this and make the necessary transition. Today&#8217;s management is too invested into the current, central role of IT department.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim France</title>
		<link>http://edge4dev.wordpress.com/2007/11/29/it-people/#comment-75</link>
		<dc:creator>Tim France</dc:creator>
		<pubDate>Fri, 30 Nov 2007 09:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://edge4dev.wordpress.com/2007/11/29/it-people/#comment-75</guid>
		<description>Nice one Damir, I hope you feel better with that one off your chest.

Do you know what your description reminds me of? The rise and fall of the architects&#039; profession.

There was a time, not so long ago, that if you needed to build anything (buildings, I mean) you had to start by appointing an architect. seeing as how they drafted the plans for the building, it was also assumed that they were in a good position to run the whole building project. Then without warning, along came a new breed: Planning Engineers. 

Two good links: &lt;a href=&quot;http://www.planningengineers.org/&quot; rel=&quot;nofollow&quot;&gt;
Planning Engineers Organisation&lt;/a&gt; and
&lt;a href=&quot;http://www.mace.co.uk/&quot; rel=&quot;nofollow&quot;&gt;Mace&lt;/a&gt;

With the appearance of Planning Engineers, it took about two seconds for everyone to realize just how crap architects had been doing at delivering projects on time/budget, and how they had been hiding it for decades. The new kids on the block &lt;i&gt;really&lt;/i&gt; knew how to manage construction projects, and how to understand what their clients wanted - within less another decade they totally pulled the carpet out from under the architects&#039; feet (laughing all the way to the bank, incidently).

Getting back to the IT-preventers, I think you are right on the button - they are just like the architects were ten years or so back. Question is though, where is the disruptive force going to come from to pull the rug from under them? I would suggest that it might not be like architects&#039; collapse at all, but will be more like Skype&#039;s disruption of  the long-distance telephone industry: Users will just vote with their feet and start adopting alternative (i.e., user-friendly) tools that don&#039;t need a nerd to make them work. They will go around the IT-preventers.

My biggest concern (now I think of it) is that once the shit hits the fan for the IT guys/girls, those very same people will move sideways into another &#039;let&#039;s have a go at this&#039; career path. Please don&#039;t let it be into my back yard!</description>
		<content:encoded><![CDATA[<p>Nice one Damir, I hope you feel better with that one off your chest.</p>
<p>Do you know what your description reminds me of? The rise and fall of the architects&#8217; profession.</p>
<p>There was a time, not so long ago, that if you needed to build anything (buildings, I mean) you had to start by appointing an architect. seeing as how they drafted the plans for the building, it was also assumed that they were in a good position to run the whole building project. Then without warning, along came a new breed: Planning Engineers. </p>
<p>Two good links: <a href="http://www.planningengineers.org/" rel="nofollow"><br />
Planning Engineers Organisation</a> and<br />
<a href="http://www.mace.co.uk/" rel="nofollow">Mace</a></p>
<p>With the appearance of Planning Engineers, it took about two seconds for everyone to realize just how crap architects had been doing at delivering projects on time/budget, and how they had been hiding it for decades. The new kids on the block <i>really</i> knew how to manage construction projects, and how to understand what their clients wanted &#8211; within less another decade they totally pulled the carpet out from under the architects&#8217; feet (laughing all the way to the bank, incidently).</p>
<p>Getting back to the IT-preventers, I think you are right on the button &#8211; they are just like the architects were ten years or so back. Question is though, where is the disruptive force going to come from to pull the rug from under them? I would suggest that it might not be like architects&#8217; collapse at all, but will be more like Skype&#8217;s disruption of  the long-distance telephone industry: Users will just vote with their feet and start adopting alternative (i.e., user-friendly) tools that don&#8217;t need a nerd to make them work. They will go around the IT-preventers.</p>
<p>My biggest concern (now I think of it) is that once the shit hits the fan for the IT guys/girls, those very same people will move sideways into another &#8216;let&#8217;s have a go at this&#8217; career path. Please don&#8217;t let it be into my back yard!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
