<?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:ymaps="http://api.maps.yahoo.com/Maps/V2/AnnotatedMaps.xsd"	>
<channel>
	<title>Comments on: The Code of Successful Websites</title>
	<atom:link href="http://www.codebelay.com/blog/2008/05/26/the-code-of-successful-websites/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codebelay.com/blog/2008/05/26/the-code-of-successful-websites/</link>
	<description>Safely Reach New Tech Heights Through Our Startup Insights</description>
	<lastBuildDate>Sun, 05 Feb 2012 01:14:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ryan</title>
		<link>http://www.codebelay.com/blog/2008/05/26/the-code-of-successful-websites/comment-page-1/#comment-5564</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Tue, 03 Jun 2008 20:49:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.codebelay.com/blog/?p=62#comment-5564</guid>
		<description>Haha, I love the comparison to the wild west.  It&#039;s very true that the biggest growth and most notable functionality are usually a product of flimsy code.  But how do you balance the sloppy requirements on early development with the inevitable need for solid maintainable code as the product grows in scale and in function?

Also, is it not possible that a clash of methodologies might also be a sign of a floundering project making desperate changes in management?</description>
		<content:encoded><![CDATA[<p>Haha, I love the comparison to the wild west.  It&#8217;s very true that the biggest growth and most notable functionality are usually a product of flimsy code.  But how do you balance the sloppy requirements on early development with the inevitable need for solid maintainable code as the product grows in scale and in function?</p>
<p>Also, is it not possible that a clash of methodologies might also be a sign of a floundering project making desperate changes in management?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.423 seconds -->

