<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Vistaprint Lessons Learned &#8211; Part 1: Software Development</title>
	<atom:link href="http://blog.mpdaugherty.com/2010/02/09/vistaprint-lessons-learned-software-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mpdaugherty.com/2010/02/09/vistaprint-lessons-learned-software-development/</link>
	<description>Mike&#039;s in China, doing tech stuff</description>
	<lastBuildDate>Mon, 26 Jul 2010 20:41:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Kendall</title>
		<link>http://blog.mpdaugherty.com/2010/02/09/vistaprint-lessons-learned-software-development/#comment-328</link>
		<dc:creator>Kendall</dc:creator>
		<pubDate>Wed, 10 Feb 2010 17:23:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mpdaugherty.com/?p=191#comment-328</guid>
		<description>&quot;Patch, patch, patch&quot; is how engineers code ;-).  Or at least the ones in my office.  They know they should abandon their legacy code, but at this point, we would pretty much have to start all over.  It&#039;s hard to convince anyone to do that since the software is more a PR tool than a money maker (it&#039;s sort of half and half), but it looks like it&#039;s 10 years old and half of it is in fortran ... I&#039;m worried about what it what it will look like and how it will run in 10 more years ...</description>
		<content:encoded><![CDATA[<p>&#8220;Patch, patch, patch&#8221; is how engineers code <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> .  Or at least the ones in my office.  They know they should abandon their legacy code, but at this point, we would pretty much have to start all over.  It&#8217;s hard to convince anyone to do that since the software is more a PR tool than a money maker (it&#8217;s sort of half and half), but it looks like it&#8217;s 10 years old and half of it is in fortran &#8230; I&#8217;m worried about what it what it will look like and how it will run in 10 more years &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
