<?xml version="1.0" ?>
<rss version="2.0">
	<channel>
		<title>Keith's Weblog: Comments on &quot;&quot;Enterprise&quot; application development&quot;</title>
		<description>Keith's Weblog: Comments on &quot;&quot;Enterprise&quot; application development&quot;, posted on January 21, 2006</description>
		<link>http://keithdevens.com/weblog/archive/2006/Jan/21/enterprise-dev</link>

		<category>Programming</category>
		<language>en-us</language>
		<image>
			<link>http://keithdevens.com/weblog</link>
			<title>Keith Devens .com</title>
			<url>http://keithdevens.com/images/kbd.gif</url>
		</image>

		<item>
			<title>by Hannibal</title>
			<link>http://keithdevens.com/weblog/archive/2006/Jan/21/enterprise-dev#comment9050</link>
			<guid isPermaLink="false">http://keithdevens.com/weblog/7867#comment9050</guid>
			<pubDate>Tue, 24 Jan 2006 02:22:15 +0000</pubDate>
			<description>&lt;p class=&quot;st-markup&quot;&gt;Enterprise application development to me isn't about issues of scale, but rather issues of flexibility. You have to move fast and be very adaptive to survive in the corporate world. Your applications can't be brittle.&lt;/p&gt;

&lt;p class=&quot;st-markup&quot;&gt;If you write fast, lean, efficient code with good tools like .NET and SQL Server, scaling is rarely an issue. &lt;/p&gt;

&lt;p class=&quot;st-markup&quot;&gt;Frameworks usually do nothing more than force you to spend a lot of time messing around with somebody else's code.&lt;/p&gt;

</description>
		</item>
	</channel>
</rss>
