<?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: Devops, complexity and anti-fragility in IT: Risk and anti-fragility</title>
	<atom:link href="http://gigaom.com/2013/01/19/devops-complexity-and-anti-fragility-in-it-risk-and-anti-fragility/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2013/01/19/devops-complexity-and-anti-fragility-in-it-risk-and-anti-fragility/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 11:31:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Joe Sanchez</title>
		<link>http://gigaom.com/2013/01/19/devops-complexity-and-anti-fragility-in-it-risk-and-anti-fragility/#comment-1321048</link>
		<dc:creator><![CDATA[Joe Sanchez]]></dc:creator>
		<pubDate>Mon, 18 Mar 2013 21:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=602310#comment-1321048</guid>
		<description><![CDATA[DevOps is not a technology or a team. It&#039;s a culture change and unfortunately only a few are getting it right because people keep getting in the way. I once heard &quot;anything with 2 heads is a monster&quot; that&#039;s why IT and Development struggle to deliver even the simplest code. The are a 2 headed monster. DevOps merges the 2 heads into one and tryings to build a culture around teams working together instead of against each other. Here&#039;s a post I wrote on the &lt;a href=&quot;http://www.vminstall.com/devops&quot; rel=&quot;nofollow&quot;&gt; Shades of DevOps&lt;/a&gt;.]]></description>
		<content:encoded><![CDATA[<p>DevOps is not a technology or a team. It&#8217;s a culture change and unfortunately only a few are getting it right because people keep getting in the way. I once heard &#8220;anything with 2 heads is a monster&#8221; that&#8217;s why IT and Development struggle to deliver even the simplest code. The are a 2 headed monster. DevOps merges the 2 heads into one and tryings to build a culture around teams working together instead of against each other. Here&#8217;s a post I wrote on the <a href="http://www.vminstall.com/devops" rel="nofollow"> Shades of DevOps</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jez Humble</title>
		<link>http://gigaom.com/2013/01/19/devops-complexity-and-anti-fragility-in-it-risk-and-anti-fragility/#comment-1302024</link>
		<dc:creator><![CDATA[Jez Humble]]></dc:creator>
		<pubDate>Tue, 22 Jan 2013 02:30:57 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=602310#comment-1302024</guid>
		<description><![CDATA[You&#039;ve met DevOps evil twin. Check out my post: &quot;there&#039;s no such thing as a devops team&quot;: http://continuousdelivery.com/2012/10/theres-no-such-thing-as-a-devops-team/]]></description>
		<content:encoded><![CDATA[<p>You&#8217;ve met DevOps evil twin. Check out my post: &#8220;there&#8217;s no such thing as a devops team&#8221;: <a href="http://continuousdelivery.com/2012/10/theres-no-such-thing-as-a-devops-team/" rel="nofollow">http://continuousdelivery.com/2012/10/theres-no-such-thing-as-a-devops-team/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sub Bose</title>
		<link>http://gigaom.com/2013/01/19/devops-complexity-and-anti-fragility-in-it-risk-and-anti-fragility/#comment-1301475</link>
		<dc:creator><![CDATA[Sub Bose]]></dc:creator>
		<pubDate>Sun, 20 Jan 2013 16:11:26 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=602310#comment-1301475</guid>
		<description><![CDATA[Dev ops is nothing more but good old shell scripting on steroids. Looks like developers don&#039;t have enough work , so they have started to muck around with System Administration. The result is actually a slower rate of change because previously what could be a simple shell script change has now to be floated to the DevOps team , who will put it on their agile voodoo dashboard, checkout from svn, make changes , check it back in, run through dev, qa and ultimately to production. On top of that they are always back logged so what used to take a day in the olden days with the Devops team it is now a two weeks process. Basically this is all part of the overall process to dehumanize our jobs.]]></description>
		<content:encoded><![CDATA[<p>Dev ops is nothing more but good old shell scripting on steroids. Looks like developers don&#8217;t have enough work , so they have started to muck around with System Administration. The result is actually a slower rate of change because previously what could be a simple shell script change has now to be floated to the DevOps team , who will put it on their agile voodoo dashboard, checkout from svn, make changes , check it back in, run through dev, qa and ultimately to production. On top of that they are always back logged so what used to take a day in the olden days with the Devops team it is now a two weeks process. Basically this is all part of the overall process to dehumanize our jobs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Martin</title>
		<link>http://gigaom.com/2013/01/19/devops-complexity-and-anti-fragility-in-it-risk-and-anti-fragility/#comment-1301403</link>
		<dc:creator><![CDATA[Paul Martin]]></dc:creator>
		<pubDate>Sun, 20 Jan 2013 02:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=602310#comment-1301403</guid>
		<description><![CDATA[Not just the arc of innovation is relevant to adoption of the &quot;everyone makes mistakes&quot; approach.  When times are interesting and sub-organisations are on the downbeat it is hard for an employee to say we should try this and see if it works; middle management can be looking over their shoulders rather than holding their heads up.]]></description>
		<content:encoded><![CDATA[<p>Not just the arc of innovation is relevant to adoption of the &#8220;everyone makes mistakes&#8221; approach.  When times are interesting and sub-organisations are on the downbeat it is hard for an employee to say we should try this and see if it works; middle management can be looking over their shoulders rather than holding their heads up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
