<?xml version="1.0" encoding="iso-8859-1"?><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: Revenue err Red light cameras</title>
	<atom:link href="http://www.saysuncle.com/2008/03/14/revenue_err_red_light_cameras/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.saysuncle.com/2008/03/14/revenue_err_red_light_cameras/</link>
	<description>Remember, I do this to entertain me... not you.</description>
	<lastBuildDate>Sun, 08 Nov 2009 18:00:44 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: existingthing</title>
		<link>http://www.saysuncle.com/2008/03/14/revenue_err_red_light_cameras/comment-page-1/#comment-196937</link>
		<dc:creator>existingthing</dc:creator>
		<pubDate>Sat, 15 Mar 2008 02:07:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.saysuncle.com/archives/2008/03/14/revenue_err_red_light_cameras/#comment-196937</guid>
		<description>Computer glitch is at least three kinds of bullshit. I worked with someone who wrote software for that kind of stuff, and it is 99.999% bulletproof coding. It&#039;s all made to be exactly the same, and to interface exactly the same way, to make it harder for people to screw up the installation. The other thing is; all of the code has built in drops so that if anything screwy happens, it automatically stops working. Even if the glitch it minor.

He complained profusely because writing code so failure-proof is very difficult.

&quot;The computer did it&quot; is an excuse that is becoming far too overused. Perhaps we need this code to be open source. So the computer did it? Then which line of code was referenced in the segfault?</description>
		<content:encoded><![CDATA[<p>Computer glitch is at least three kinds of bullshit. I worked with someone who wrote software for that kind of stuff, and it is 99.999% bulletproof coding. It&#8217;s all made to be exactly the same, and to interface exactly the same way, to make it harder for people to screw up the installation. The other thing is; all of the code has built in drops so that if anything screwy happens, it automatically stops working. Even if the glitch it minor.</p>
<p>He complained profusely because writing code so failure-proof is very difficult.</p>
<p>&#8220;The computer did it&#8221; is an excuse that is becoming far too overused. Perhaps we need this code to be open source. So the computer did it? Then which line of code was referenced in the segfault?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thirdpower</title>
		<link>http://www.saysuncle.com/2008/03/14/revenue_err_red_light_cameras/comment-page-1/#comment-196867</link>
		<dc:creator>thirdpower</dc:creator>
		<pubDate>Fri, 14 Mar 2008 13:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.saysuncle.com/archives/2008/03/14/revenue_err_red_light_cameras/#comment-196867</guid>
		<description>I happened to be in an IL committee meeting when they were debating a camera bill. The advocate specifically said it wouldn&#039;t be used as a revenue generator. The entire room laughed, including the committee members.  It passed anyway.</description>
		<content:encoded><![CDATA[<p>I happened to be in an IL committee meeting when they were debating a camera bill. The advocate specifically said it wouldn&#8217;t be used as a revenue generator. The entire room laughed, including the committee members.  It passed anyway.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
