<?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: Operations is a Competitive Advantage</title>
	<atom:link href="http://sysadminry.wordpress.com/2008/01/31/operations-is-a-competitive-advantage/feed/" rel="self" type="application/rss+xml" />
	<link>http://sysadminry.wordpress.com/2008/01/31/operations-is-a-competitive-advantage/</link>
	<description>All about System Administration</description>
	<pubDate>Thu, 07 Aug 2008 22:24:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: David</title>
		<link>http://sysadminry.wordpress.com/2008/01/31/operations-is-a-competitive-advantage/#comment-5</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 19 Feb 2008 19:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://sysadminry.wordpress.com/?p=5#comment-5</guid>
		<description>I've got the entry opened up in a tab to read....its a research day for me, and I'm exploring Spring Webflow and how it differs from Seam - and which one fits into our environment the best.  

The gut reaction to this that I had was lets first start with defining what is desktop support, versus server support, versus application support.  Many times the people making the decisions don't have a very good grasp on what those three categories are, and if it make sense for different groups to handle this.  

And often the case is the person who they assign to be responsible for all things that speak 0s or 1s doesn't want to disappoint by telling them that while it makes since for A and B to be under them, it might be better if C was handled by this group.  "We can work with them, but really they need a technical team under them to handle ...blah...."</description>
		<content:encoded><![CDATA[<p>I&#8217;ve got the entry opened up in a tab to read&#8230;.its a research day for me, and I&#8217;m exploring Spring Webflow and how it differs from Seam - and which one fits into our environment the best.  </p>
<p>The gut reaction to this that I had was lets first start with defining what is desktop support, versus server support, versus application support.  Many times the people making the decisions don&#8217;t have a very good grasp on what those three categories are, and if it make sense for different groups to handle this.  </p>
<p>And often the case is the person who they assign to be responsible for all things that speak 0s or 1s doesn&#8217;t want to disappoint by telling them that while it makes since for A and B to be under them, it might be better if C was handled by this group.  &#8220;We can work with them, but really they need a technical team under them to handle &#8230;blah&#8230;.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
