<?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"
	>
<channel>
	<title>Comments on: Tools of The Effective Developer: Make It Work - First!</title>
	<atom:link href="http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/</link>
	<description>Hans-Eric Grönlund on software development</description>
	<pubDate>Thu, 16 Oct 2008 04:33:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: www.hans-eric.com &#187; Blog Archive &#187; Tools of The Effective Developer: Touch Typing</title>
		<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-1256</link>
		<dc:creator>www.hans-eric.com &#187; Blog Archive &#187; Tools of The Effective Developer: Touch Typing</dc:creator>
		<pubDate>Thu, 06 Dec 2007 15:30:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-1256</guid>
		<description>[...] Tools of The Effective Developer: Make It Work - First! [...]</description>
		<content:encoded><![CDATA[<p>[...] Tools of The Effective Developer: Make It Work - First! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: www.hans-eric.com &#187; Blog Archive &#187; Tools of The Effective Developer: Rule of Three!</title>
		<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-1226</link>
		<dc:creator>www.hans-eric.com &#187; Blog Archive &#187; Tools of The Effective Developer: Rule of Three!</dc:creator>
		<pubDate>Mon, 03 Dec 2007 14:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-1226</guid>
		<description>[...] Tools of The Effective Developer: Make It Work - First! [...]</description>
		<content:encoded><![CDATA[<p>[...] Tools of The Effective Developer: Make It Work - First! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans-Eric</title>
		<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-548</link>
		<dc:creator>Hans-Eric</dc:creator>
		<pubDate>Fri, 02 Nov 2007 08:34:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-548</guid>
		<description>"but not at the cost of creating whizbang frameworks when much less is required"

Right on!</description>
		<content:encoded><![CDATA[<p>&#8220;but not at the cost of creating whizbang frameworks when much less is required&#8221;</p>
<p>Right on!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans-Eric</title>
		<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-547</link>
		<dc:creator>Hans-Eric</dc:creator>
		<pubDate>Fri, 02 Nov 2007 08:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-547</guid>
		<description>That's another way to put it :-)</description>
		<content:encoded><![CDATA[<p>That&#8217;s another way to put it <img src='http://www.hans-eric.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans-Eric</title>
		<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-546</link>
		<dc:creator>Hans-Eric</dc:creator>
		<pubDate>Fri, 02 Nov 2007 08:28:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-546</guid>
		<description>Thank you!
Your post is excellent.</description>
		<content:encoded><![CDATA[<p>Thank you!<br />
Your post is excellent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-540</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 01 Nov 2007 18:27:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-540</guid>
		<description>The two kinds of programmers are
1. Messy Programmer (under or over engineered), and
2. Neat Programmer (who also clean up others' messes).

The second category is careful balance of all the conflicting requirements (stated and unstated).  Yes, most programmers fall into the Messy category.  They leave behind an unmaintainable mess.

However, it is imprecise to describe Messy Programmers with positive words like simple and perfect.  Most of the time the "simple" programmer is writing code that ignores real-world use.  He makes production systems that crash easily and no one can figure out why.  The "perfect" programmer writes code that no one can decipher.  He also makes production systems that crash often and no one can figure out why.

The person I call the Neat Programmer is neither fast nor slow; he rides the middle ground.  He ensures that his code is understandable,  maintainable, extendable, and testable--but not at the cost of creating whizbang frameworks when much less is required.</description>
		<content:encoded><![CDATA[<p>The two kinds of programmers are<br />
1. Messy Programmer (under or over engineered), and<br />
2. Neat Programmer (who also clean up others&#8217; messes).</p>
<p>The second category is careful balance of all the conflicting requirements (stated and unstated).  Yes, most programmers fall into the Messy category.  They leave behind an unmaintainable mess.</p>
<p>However, it is imprecise to describe Messy Programmers with positive words like simple and perfect.  Most of the time the &#8220;simple&#8221; programmer is writing code that ignores real-world use.  He makes production systems that crash easily and no one can figure out why.  The &#8220;perfect&#8221; programmer writes code that no one can decipher.  He also makes production systems that crash often and no one can figure out why.</p>
<p>The person I call the Neat Programmer is neither fast nor slow; he rides the middle ground.  He ensures that his code is understandable,  maintainable, extendable, and testable&#8211;but not at the cost of creating whizbang frameworks when much less is required.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Hammel</title>
		<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-538</link>
		<dc:creator>Jeff Hammel</dc:creator>
		<pubDate>Thu, 01 Nov 2007 16:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-538</guid>
		<description>There are two kinds of developers:  those that try to write perfect code and those with experience.</description>
		<content:encoded><![CDATA[<p>There are two kinds of developers:  those that try to write perfect code and those with experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martijn Faassen</title>
		<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-537</link>
		<dc:creator>Martijn Faassen</dc:creator>
		<pubDate>Thu, 01 Nov 2007 14:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-537</guid>
		<description>Good posting. I call these tendencies under and over-engineering. I started writing a comment about this here, but it got long, so I put it in my own blog: &lt;a href="http://faassen.n--tree.net/blog/view/weblog/2007/11/01/0" rel="nofollow"&gt;under-engineering, over-engineering, right-engineering&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Good posting. I call these tendencies under and over-engineering. I started writing a comment about this here, but it got long, so I put it in my own blog: <a href="http://faassen.n--tree.net/blog/view/weblog/2007/11/01/0" rel="nofollow">under-engineering, over-engineering, right-engineering</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabe</title>
		<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-535</link>
		<dc:creator>Gabe</dc:creator>
		<pubDate>Thu, 01 Nov 2007 13:44:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-535</guid>
		<description>Good idea - let them see some functionality, but explain that it isn't complete yet until you get at least one run through optimizing it. Thanks!</description>
		<content:encoded><![CDATA[<p>Good idea - let them see some functionality, but explain that it isn&#8217;t complete yet until you get at least one run through optimizing it. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans-Eric</title>
		<link>http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-526</link>
		<dc:creator>Hans-Eric</dc:creator>
		<pubDate>Thu, 01 Nov 2007 08:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/10/29/tools-of-the-effective-developer-make-it-work-first/#comment-526</guid>
		<description>Good point! 

I meant "least effort", but that's how I define simplicity. The simplest solution, as you pointed out, is not necessarily the first that comes to mind.</description>
		<content:encoded><![CDATA[<p>Good point! </p>
<p>I meant &#8220;least effort&#8221;, but that&#8217;s how I define simplicity. The simplest solution, as you pointed out, is not necessarily the first that comes to mind.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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