<?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: When you can&#8217;t just start over</title>
	<atom:link href="http://meganmcdermott.com/2008/01/15/when-you-cant-just-start-over/feed/" rel="self" type="application/rss+xml" />
	<link>http://meganmcdermott.com/2008/01/15/when-you-cant-just-start-over/</link>
	<description>Web design and that</description>
	<lastBuildDate>Fri, 04 May 2012 23:55:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ruben</title>
		<link>http://meganmcdermott.com/2008/01/15/when-you-cant-just-start-over/comment-page-1/#comment-15535</link>
		<dc:creator>Ruben</dc:creator>
		<pubDate>Fri, 18 Jan 2008 16:24:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.meganmcdermott.com/2008/01/15/when-you-cant-just-start-over/#comment-15535</guid>
		<description>I don&#039;t do much CSS or client side but I know the general feeling about having to fix code that stinks. I have been seriously thinking about to just decline to do that kind of work. The general problem here of course is that people that pay for software never read code. To even think that they should have some appreciation of beautiful code.... well, it is not about to happen any day soon. As long as the code does the work it is good code.... The only way to their ears is to talk about maintenance cost. &quot;This code sucks and I would have been able to do the change twice as fast if the code had been nice and tidy.&quot; The reply most often is a resigned: &quot;ok - but your fix is still cheaper than the rewrite.&quot;. 

Another related thing that distrubs me is when I write a nice piece of code and sign it with my name. Then some other person ruins my nice code with nasty fixes and doesn&#039;t sign his work so it still appears as if I actually coded the thing. (Ok - the versioning system keeps track of this but still....)</description>
		<content:encoded><![CDATA[<p>I don&#8217;t do much CSS or client side but I know the general feeling about having to fix code that stinks. I have been seriously thinking about to just decline to do that kind of work. The general problem here of course is that people that pay for software never read code. To even think that they should have some appreciation of beautiful code&#8230;. well, it is not about to happen any day soon. As long as the code does the work it is good code&#8230;. The only way to their ears is to talk about maintenance cost. &#8220;This code sucks and I would have been able to do the change twice as fast if the code had been nice and tidy.&#8221; The reply most often is a resigned: &#8220;ok &#8211; but your fix is still cheaper than the rewrite.&#8221;. </p>
<p>Another related thing that distrubs me is when I write a nice piece of code and sign it with my name. Then some other person ruins my nice code with nasty fixes and doesn&#8217;t sign his work so it still appears as if I actually coded the thing. (Ok &#8211; the versioning system keeps track of this but still&#8230;.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam H</title>
		<link>http://meganmcdermott.com/2008/01/15/when-you-cant-just-start-over/comment-page-1/#comment-15484</link>
		<dc:creator>Adam H</dc:creator>
		<pubDate>Wed, 16 Jan 2008 14:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.meganmcdermott.com/2008/01/15/when-you-cant-just-start-over/#comment-15484</guid>
		<description>Do what I do. Start working on the replacement version in free moments so eventually you can roll it out from scratch. It is like a branch in the versioning, patches can still be applied to the old branch but the new branch is where all the development is going on.

Good luck with that!</description>
		<content:encoded><![CDATA[<p>Do what I do. Start working on the replacement version in free moments so eventually you can roll it out from scratch. It is like a branch in the versioning, patches can still be applied to the old branch but the new branch is where all the development is going on.</p>
<p>Good luck with that!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

