<?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/"
		>
<channel>
	<title>Comments on: Programming is like sex</title>
	<atom:link href="http://www.twobraincells.com/2006/07/09/programming-is-like-sex/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.twobraincells.com/2006/07/09/programming-is-like-sex/</link>
	<description></description>
	<lastBuildDate>Mon, 10 Oct 2011 10:12:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: wild electrons</title>
		<link>http://www.twobraincells.com/2006/07/09/programming-is-like-sex/comment-page-1/#comment-23</link>
		<dc:creator>wild electrons</dc:creator>
		<pubDate>Wed, 12 Jul 2006 18:28:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.twobraincells.com/2006/07/09/programming-is-like-sex/#comment-23</guid>
		<description>&quot;One little thing going wrong can ruin everything.&quot;

The first time I incorporated a system (client-side and server-side) to check for (and then download and install) program updates automatically, I got one tiny little detail completely wrong. And this caused much havoc for me and much havoc for my users :) Until the day I stopped supporting that program, I had to create hugely inelegant work-arounds on the server side code (and in subsequent versions&#039; client-side code), and wished I&#039;d never done that silly (1-line) mistake...</description>
		<content:encoded><![CDATA[<p>&#8220;One little thing going wrong can ruin everything.&#8221;</p>
<p>The first time I incorporated a system (client-side and server-side) to check for (and then download and install) program updates automatically, I got one tiny little detail completely wrong. And this caused much havoc for me and much havoc for my users :) Until the day I stopped supporting that program, I had to create hugely inelegant work-arounds on the server side code (and in subsequent versions&#8217; client-side code), and wished I&#8217;d never done that silly (1-line) mistake&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

