<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Developer Productivity</title>
	<link>http://blog.springsource.com/arjen/archives/2006/02/14/developer-productivity/</link>
	<description>A blog about programming in .NET and Java</description>
	<pubDate>Thu, 20 Nov 2008 13:29:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Thought Leadership</title>
		<link>http://blog.springsource.com/arjen/archives/2006/02/14/developer-productivity/#comment-341</link>
		<pubDate>Fri, 03 Mar 2006 12:18:06 +0000</pubDate>
		<guid>http://blog.springsource.com/arjen/archives/2006/02/14/developer-productivity/#comment-341</guid>
					<description>&lt;strong&gt;Agilists who practice Command and Control&lt;/strong&gt;

In my travels I have ran across lots of folks who have savagely read many of the books on enterprise architecture and still have gotten it wrong...</description>
		<content:encoded><![CDATA[<p><strong>Agilists who practice Command and Control</strong></p>
<p>In my travels I have ran across lots of folks who have savagely read many of the books on enterprise architecture and still have gotten it wrong&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Alef Arendsen</title>
		<link>http://blog.springsource.com/arjen/archives/2006/02/14/developer-productivity/#comment-335</link>
		<pubDate>Wed, 15 Feb 2006 10:20:49 +0000</pubDate>
		<guid>http://blog.springsource.com/arjen/archives/2006/02/14/developer-productivity/#comment-335</guid>
					<description>I agree it's a good thing if a framework 'knows what you want' to some extent. However, tools, should never do things automagically, without offering the developer insight in what the framework is actually doing behind the scenes. Not doing so would result in ambiguous results and intensive debug sessions only finding out after hours that the framework did something you didn't want it to do.</description>
		<content:encoded><![CDATA[<p>I agree it&#8217;s a good thing if a framework &#8216;knows what you want&#8217; to some extent. However, tools, should never do things automagically, without offering the developer insight in what the framework is actually doing behind the scenes. Not doing so would result in ambiguous results and intensive debug sessions only finding out after hours that the framework did something you didn&#8217;t want it to do.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
