<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://benchelf.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Ben Chelf</title>
 <link>http://benchelf.sys-con.com/</link>
 <description>Latest News from Ben Chelf</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Mon, 30 Nov 2009 05:45:43 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>The Paradox of Writing Perfect Code</title>
 <link>http://benchelf.sys-con.com/node/325148</link>
 <description>Don&#039;t you love looking at a good piece of code? I&#039;m talking about the kind of code where the design is so sound that the code practically wrote itself, where there were no nasty surprises at implementation, where it was 100% feature complete and bug-free, and you didn&#039;t have to patch it up a bunch of times. Maybe I&#039;m squarely in the land of Santa Claus and the Easter Bunny, but I believe, deep down, all developers want to write that perfect piece of code. Unfortunately, real life has other ideas. Deadlines, unclear or conflicting requirements, ridiculous scope, being human - all these things keep us from the promised land of perfect code.&lt;p&gt;&lt;a href=&quot;http://benchelf.sys-con.com/node/325148&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 29 Jan 2007 17:15:00 EST</pubDate>
 <guid isPermaLink="true">http://benchelf.sys-con.com/node/325148</guid>
 <comments>http://benchelf.sys-con.com/node/325148#feedback</comments>
</item>
</channel>
</rss>
