<?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: Catching up&#8230;</title>
	<atom:link href="http://www.mikeandrews.com/2008/08/16/catching-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mikeandrews.com/2008/08/16/catching-up/</link>
	<description></description>
	<lastBuildDate>Fri, 09 Apr 2010 12:01:55 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike</title>
		<link>http://www.mikeandrews.com/2008/08/16/catching-up/comment-page-1/#comment-221</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 21 Aug 2008 21:50:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikeandrews.com/2008/08/16/catching-up/#comment-221</guid>
		<description>I could not agree with you more.  However, I really don&#039;t think that it&#039;s going to b e easy - there&#039;s just too much code out there and investment (intellectually, as well as monetary) in the existing ways we build software.  The legacy stuff in and of itself will hold us back from any meaningful change any time soon.

Don&#039;t get me wrong, I would love to see it, and feel that several companies have missed great opportunities to throw a lot of things out that don&#039;t work and as you say start afresh.  All the time we are in a &quot;penetrate and patch&quot; approach (which is far too many) things are always going to be flawed.</description>
		<content:encoded><![CDATA[<p>I could not agree with you more.  However, I really don&#8217;t think that it&#8217;s going to b e easy &#8211; there&#8217;s just too much code out there and investment (intellectually, as well as monetary) in the existing ways we build software.  The legacy stuff in and of itself will hold us back from any meaningful change any time soon.</p>
<p>Don&#8217;t get me wrong, I would love to see it, and feel that several companies have missed great opportunities to throw a lot of things out that don&#8217;t work and as you say start afresh.  All the time we are in a &#8220;penetrate and patch&#8221; approach (which is far too many) things are always going to be flawed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Ristić</title>
		<link>http://www.mikeandrews.com/2008/08/16/catching-up/comment-page-1/#comment-219</link>
		<dc:creator>Ivan Ristić</dc:creator>
		<pubDate>Mon, 18 Aug 2008 19:27:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikeandrews.com/2008/08/16/catching-up/#comment-219</guid>
		<description>Mike, just for the record, I don&#039;t give special treatment to design flaws. They are defects too, just of different kind. Thus, I wasn&#039;t talking about defects in code specifically, but any undesireable behaviour and appearance in the finished product. I think programming--in the way we are practicing it today--is too difficult. We need to start afresh, and find a way to make it easier. Maybe then we would have more success in building secure systems.</description>
		<content:encoded><![CDATA[<p>Mike, just for the record, I don&#8217;t give special treatment to design flaws. They are defects too, just of different kind. Thus, I wasn&#8217;t talking about defects in code specifically, but any undesireable behaviour and appearance in the finished product. I think programming&#8211;in the way we are practicing it today&#8211;is too difficult. We need to start afresh, and find a way to make it easier. Maybe then we would have more success in building secure systems.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
