<?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: Would You Trust Your Life To Your Code?</title>
	<atom:link href="http://www.basilv.com/psd/blog/2009/would-you-trust-your-life-to-your-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.basilv.com/psd/blog/2009/would-you-trust-your-life-to-your-code</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 03:57:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Basil Vandegriend</title>
		<link>http://www.basilv.com/psd/blog/2009/would-you-trust-your-life-to-your-code/comment-page-1#comment-101313</link>
		<dc:creator>Basil Vandegriend</dc:creator>
		<pubDate>Fri, 04 Dec 2009 16:15:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/?p=445#comment-101313</guid>
		<description>@Daramarak, you are absolutely correct that I ignored the role of the organization / management in providing the appropriate support. This article was targeted solely at developers taking responsibility for the quality of the code they produce. I have seen many cases when given sufficient time developers were still not able to produce high-quality code. Management, of course, must provide sufficient time or must carefully define the desired trade-off in quality, which gets into the debate about &quot;good enough&quot; software. This topic can easily be another article or three, which is one reason I did not want to touch on it in this post.</description>
		<content:encoded><![CDATA[<p>@Daramarak, you are absolutely correct that I ignored the role of the organization / management in providing the appropriate support. This article was targeted solely at developers taking responsibility for the quality of the code they produce. I have seen many cases when given sufficient time developers were still not able to produce high-quality code. Management, of course, must provide sufficient time or must carefully define the desired trade-off in quality, which gets into the debate about &#8220;good enough&#8221; software. This topic can easily be another article or three, which is one reason I did not want to touch on it in this post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daramarak</title>
		<link>http://www.basilv.com/psd/blog/2009/would-you-trust-your-life-to-your-code/comment-page-1#comment-101297</link>
		<dc:creator>Daramarak</dc:creator>
		<pubDate>Fri, 04 Dec 2009 10:57:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/?p=445#comment-101297</guid>
		<description>But there is more to it than the developer. You might *want* to assert that the code is 100% ok, but when your employer constantly wants you to deliver yesterday, you have to choose between satisfying your employer or your conscience, where the latter might cost you your job.

I think it is much more about challenging the industry rather than the developer. When the industry stops tolerating errors, the developer might start delivering. Until then, the developer produces what he is able to with the resources he has, or worst case, what he can get away with.</description>
		<content:encoded><![CDATA[<p>But there is more to it than the developer. You might *want* to assert that the code is 100% ok, but when your employer constantly wants you to deliver yesterday, you have to choose between satisfying your employer or your conscience, where the latter might cost you your job.</p>
<p>I think it is much more about challenging the industry rather than the developer. When the industry stops tolerating errors, the developer might start delivering. Until then, the developer produces what he is able to with the resources he has, or worst case, what he can get away with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matthias</title>
		<link>http://www.basilv.com/psd/blog/2009/would-you-trust-your-life-to-your-code/comment-page-1#comment-100766</link>
		<dc:creator>matthias</dc:creator>
		<pubDate>Tue, 24 Nov 2009 15:30:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/?p=445#comment-100766</guid>
		<description>Simple answer: No. I&#039;m sorry.</description>
		<content:encoded><![CDATA[<p>Simple answer: No. I&#8217;m sorry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Foukarakis</title>
		<link>http://www.basilv.com/psd/blog/2009/would-you-trust-your-life-to-your-code/comment-page-1#comment-100763</link>
		<dc:creator>Michael Foukarakis</dc:creator>
		<pubDate>Tue, 24 Nov 2009 14:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/?p=445#comment-100763</guid>
		<description>I don&#039;t even trust my PC to my code, unless absolutely necessary. The great tragedy with software engineering is that we are taught that failures aren&#039;t critical - if your program segfaults, hey, just load it in a debugger and kludge until it works..</description>
		<content:encoded><![CDATA[<p>I don&#8217;t even trust my PC to my code, unless absolutely necessary. The great tragedy with software engineering is that we are taught that failures aren&#8217;t critical &#8211; if your program segfaults, hey, just load it in a debugger and kludge until it works..</p>
]]></content:encoded>
	</item>
</channel>
</rss>

