<?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: What makes a &#8216;good&#8217; programmer?</title>
	<atom:link href="http://www.hasemanonmobile.com/2009/08/10/what-makes-a-good-programmer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hasemanonmobile.com/2009/08/10/what-makes-a-good-programmer/</link>
	<description>Mobile Development, Software, and anything else</description>
	<lastBuildDate>Tue, 01 Dec 2009 17:12:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Programmer Competency (Part 3) &#171; Mike Vallotton&#8217;s Blog</title>
		<link>http://www.hasemanonmobile.com/2009/08/10/what-makes-a-good-programmer/comment-page-1/#comment-19</link>
		<dc:creator>Programmer Competency (Part 3) &#171; Mike Vallotton&#8217;s Blog</dc:creator>
		<pubDate>Wed, 19 Aug 2009 03:27:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.hasemanonmobile.com/?p=32#comment-19</guid>
		<description>[...] think that this hasemanonmobile.com post sums it up succinctly, though. Really, the only two things that you need to be a good developer are [...]</description>
		<content:encoded><![CDATA[<p>[...] think that this hasemanonmobile.com post sums it up succinctly, though. Really, the only two things that you need to be a good developer are [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Haseman</title>
		<link>http://www.hasemanonmobile.com/2009/08/10/what-makes-a-good-programmer/comment-page-1/#comment-14</link>
		<dc:creator>Haseman</dc:creator>
		<pubDate>Tue, 11 Aug 2009 19:45:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.hasemanonmobile.com/?p=32#comment-14</guid>
		<description>Great points Magice,

I would say, however, that your criticism boils down to the tactic of asking &#039;why&#039; over and over again.  I could have broken down exactly what I meant by &#039;Trust&#039; or &#039;Rules&#039; but these are fairly well known ideals.  Philosophers have written books about the meaning and nuance of both these subjects.  They are, at least, for the purposes of writing and maintaining software, pretty well known and understood.  However, as you point out, there&#039;s always room for better and more through definitions.

In the end, and I could see how I missed a little at this one, it was my desire to reveal that one must evaluate much more than programming traits when evaluating an engineer.  We can quibble about exactly what those traits are (and I look forward to doing more of that in the future) but perhaps we could agree on just that small thing for now?</description>
		<content:encoded><![CDATA[<p>Great points Magice,</p>
<p>I would say, however, that your criticism boils down to the tactic of asking &#8216;why&#8217; over and over again.  I could have broken down exactly what I meant by &#8216;Trust&#8217; or &#8216;Rules&#8217; but these are fairly well known ideals.  Philosophers have written books about the meaning and nuance of both these subjects.  They are, at least, for the purposes of writing and maintaining software, pretty well known and understood.  However, as you point out, there&#8217;s always room for better and more through definitions.</p>
<p>In the end, and I could see how I missed a little at this one, it was my desire to reveal that one must evaluate much more than programming traits when evaluating an engineer.  We can quibble about exactly what those traits are (and I look forward to doing more of that in the future) but perhaps we could agree on just that small thing for now?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Magice</title>
		<link>http://www.hasemanonmobile.com/2009/08/10/what-makes-a-good-programmer/comment-page-1/#comment-13</link>
		<dc:creator>Magice</dc:creator>
		<pubDate>Tue, 11 Aug 2009 19:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.hasemanonmobile.com/?p=32#comment-13</guid>
		<description>There is something wrong with both of your traits for good programmers. Both of them lack too much.

Let&#039;s talk about trust. How do you build trust? By talking people into it? Um, really? Sorry, but I much prefer people who cannot talk me into their grand-designs (communicate), but is responsible and caring, as well as be proud enough about their career that they always uphold the utmost standard for their products.

Furthermore, I always hate the talking about abandoning rules. Assume that one of our rules is to produce clear, easy to understand code. Because the deadline is tomorrow, am I entitled to break that rule, to meet the deadline? The rules are there for a reason. If the rules are insufficient, then let&#039;s create new set of them, and adhere to that set of rules. Trying to work around is just senseless and dangerous, if not irresponsible.

In the end, well, you still have not answer the question: what makes great programmers?</description>
		<content:encoded><![CDATA[<p>There is something wrong with both of your traits for good programmers. Both of them lack too much.</p>
<p>Let&#8217;s talk about trust. How do you build trust? By talking people into it? Um, really? Sorry, but I much prefer people who cannot talk me into their grand-designs (communicate), but is responsible and caring, as well as be proud enough about their career that they always uphold the utmost standard for their products.</p>
<p>Furthermore, I always hate the talking about abandoning rules. Assume that one of our rules is to produce clear, easy to understand code. Because the deadline is tomorrow, am I entitled to break that rule, to meet the deadline? The rules are there for a reason. If the rules are insufficient, then let&#8217;s create new set of them, and adhere to that set of rules. Trying to work around is just senseless and dangerous, if not irresponsible.</p>
<p>In the end, well, you still have not answer the question: what makes great programmers?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Rodenbaugh</title>
		<link>http://www.hasemanonmobile.com/2009/08/10/what-makes-a-good-programmer/comment-page-1/#comment-12</link>
		<dc:creator>Dave Rodenbaugh</dc:creator>
		<pubDate>Tue, 11 Aug 2009 14:46:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.hasemanonmobile.com/?p=32#comment-12</guid>
		<description>Glad to see an article that finally moves past the &quot;Stump the Chump&quot; mentality of finding a good engineer.  Great article!</description>
		<content:encoded><![CDATA[<p>Glad to see an article that finally moves past the &#8220;Stump the Chump&#8221; mentality of finding a good engineer.  Great article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Rue</title>
		<link>http://www.hasemanonmobile.com/2009/08/10/what-makes-a-good-programmer/comment-page-1/#comment-11</link>
		<dc:creator>Martin Rue</dc:creator>
		<pubDate>Tue, 11 Aug 2009 14:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.hasemanonmobile.com/?p=32#comment-11</guid>
		<description>Couldn&#039;t agree more. 

Your points emphasise why the &#039;quick fire&#039; round in an interview is pretty much useless in determining whether a canditate is a good fit.

A candidate that can answer all the questions is just lucky (we all have gaps in our knowledge), and when their luck runs out, it&#039;s how they approach the problem and people around them in finding the solution that matters most.</description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t agree more. </p>
<p>Your points emphasise why the &#8216;quick fire&#8217; round in an interview is pretty much useless in determining whether a canditate is a good fit.</p>
<p>A candidate that can answer all the questions is just lucky (we all have gaps in our knowledge), and when their luck runs out, it&#8217;s how they approach the problem and people around them in finding the solution that matters most.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry</title>
		<link>http://www.hasemanonmobile.com/2009/08/10/what-makes-a-good-programmer/comment-page-1/#comment-10</link>
		<dc:creator>Larry</dc:creator>
		<pubDate>Tue, 11 Aug 2009 13:53:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.hasemanonmobile.com/?p=32#comment-10</guid>
		<description>Let&#039;s not forget the use of the code.  There is prototyping which is akin to the Cook, and then when you need to build a fully developed, scalable, securitized etc etc, then you need to be the Baker.</description>
		<content:encoded><![CDATA[<p>Let&#8217;s not forget the use of the code.  There is prototyping which is akin to the Cook, and then when you need to build a fully developed, scalable, securitized etc etc, then you need to be the Baker.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
