<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Hiring Great Developers?</title>
	<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/</link>
	<description>Lidor Wyssocky's Blog on Optimizing Software Development</description>
	<pubDate>Wed, 20 Aug 2008 12:46:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Hiring Great Developers? by: 彼女</title>
		<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-51475</link>
		<pubDate>Sat, 12 Jul 2008 01:00:41 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-51475</guid>
					<description>彼女を作る具体的実践的方法
彼女の作り方研究会
　くちこみ　詐欺　口コミ　レビュー　クチコミ　評判 情報局
&lt;a href=&quot;http://www.100lover.com/&quot; rel=&quot;nofollow&quot;&gt;彼女&lt;/a&gt;</description>
		<content:encoded><![CDATA[	<p>彼女を作る具体的実践的方法<br />
彼女の作り方研究会<br />
　くちこみ　詐欺　口コミ　レビュー　クチコミ　評判 情報局<br />
<a href="http://www.100lover.com/" rel="nofollow">彼女</a>
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Hiring Great Developers? by: Insurance Agents and Insurance Services</title>
		<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-26428</link>
		<pubDate>Mon, 05 Nov 2007 23:09:18 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-26428</guid>
					<description>&lt;strong&gt;Insurance Agents and Insurance Services&lt;/strong&gt;

I couldn't understand some parts of this article, but it sounds interesting</description>
		<content:encoded><![CDATA[	<p><strong>Insurance Agents and Insurance Services</strong></p>
	<p>I couldn&#8217;t understand some parts of this article, but it sounds interesting
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Hiring Great Developers? by: Ryan Elisei</title>
		<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2201</link>
		<pubDate>Mon, 09 Oct 2006 14:33:29 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2201</guid>
					<description>*bump*
Anon: (October 2nd, 2006 at 6:38 am) - Aparently coward-ware :-)</description>
		<content:encoded><![CDATA[	<p>*bump*<br />
Anon: (October 2nd, 2006 at 6:38 am) - Aparently coward-ware :-)
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Hiring Great Developers? by: Kamonohashi</title>
		<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2142</link>
		<pubDate>Fri, 06 Oct 2006 07:08:49 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2142</guid>
					<description>sojapan, $50k? Mine is something like that, and I always thought it sucks... After all, why shouldn't it? I am a foreigner, I don't speak the language, I never went to any famous college, and my employer need to worry about my working visa each year and so on. One of my colleagues (also a foreigner) left for another company which pays him about $100K, at least that's what he says.</description>
		<content:encoded><![CDATA[	<p>sojapan, $50k? Mine is something like that, and I always thought it sucks&#8230; After all, why shouldn&#8217;t it? I am a foreigner, I don&#8217;t speak the language, I never went to any famous college, and my employer need to worry about my working visa each year and so on. One of my colleagues (also a foreigner) left for another company which pays him about $100K, at least that&#8217;s what he says.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Hiring Great Developers? by: John Price</title>
		<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2111</link>
		<pubDate>Wed, 04 Oct 2006 17:57:48 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2111</guid>
					<description>As Goran says, I think the answer to the &quot;hire the best&quot; vs. &quot;grow what you've got&quot; lies somewhere between the two extremes.

People seem to focus on one metric: &quot;how good is this developer&quot; and then suggest that (if you're in the &quot;grow&quot; camp) you should work to mentor them or (if you're in the &quot;hire&quot; camp) get rid of them and hire somebody better.

The metric that people are neglecting is &quot;how interested in becoming a better developer is this person?&quot;  A crappy developer who has no interest in becoming a better developer isn't going to be a good candidate for &quot;growing&quot;.  Even a developer with a lot of experience who isn't interested in improving themself probably isn't a great hire.  On the other hand, an inexperienced college grad with a solid understanding of the basics and a genuine interest in becoming a professional is prime mentoring material.</description>
		<content:encoded><![CDATA[	<p>As Goran says, I think the answer to the &#8220;hire the best&#8221; vs. &#8220;grow what you&#8217;ve got&#8221; lies somewhere between the two extremes.</p>
	<p>People seem to focus on one metric: &#8220;how good is this developer&#8221; and then suggest that (if you&#8217;re in the &#8220;grow&#8221; camp) you should work to mentor them or (if you&#8217;re in the &#8220;hire&#8221; camp) get rid of them and hire somebody better.</p>
	<p>The metric that people are neglecting is &#8220;how interested in becoming a better developer is this person?&#8221;  A crappy developer who has no interest in becoming a better developer isn&#8217;t going to be a good candidate for &#8220;growing&#8221;.  Even a developer with a lot of experience who isn&#8217;t interested in improving themself probably isn&#8217;t a great hire.  On the other hand, an inexperienced college grad with a solid understanding of the basics and a genuine interest in becoming a professional is prime mentoring material.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Hiring Great Developers? by: Ryan Elisei</title>
		<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2109</link>
		<pubDate>Wed, 04 Oct 2006 13:22:46 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2109</guid>
					<description>The top 1% won't find you. You have to find them.

If I want Linus Torvalds on my team, I'm going to have to hire charismatic, industry-famous experts to woo him. For the honor of lavishing him with gifts I would expect to pay 3-5x the market rate. If your regular technical project managers make $70k, expect to pay 210-350k for the cream of the crop.

I would be surprised if anyone here could talk their boss into even $20k more than the market rate. If Jesus Christ walked in for an interview, about the only thing that would pique your boss's interest would his savings on health insurance. So my advice is, forget about purchasing the top 1%. Create a cool product and attract them. Create a culture that experts love to be around.</description>
		<content:encoded><![CDATA[	<p>The top 1% won&#8217;t find you. You have to find them.</p>
	<p>If I want Linus Torvalds on my team, I&#8217;m going to have to hire charismatic, industry-famous experts to woo him. For the honor of lavishing him with gifts I would expect to pay 3-5x the market rate. If your regular technical project managers make $70k, expect to pay 210-350k for the cream of the crop.</p>
	<p>I would be surprised if anyone here could talk their boss into even $20k more than the market rate. If Jesus Christ walked in for an interview, about the only thing that would pique your boss&#8217;s interest would his savings on health insurance. So my advice is, forget about purchasing the top 1%. Create a cool product and attract them. Create a culture that experts love to be around.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Hiring Great Developers? by: Goran</title>
		<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2104</link>
		<pubDate>Wed, 04 Oct 2006 07:58:09 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2104</guid>
					<description>Opposing forces (hiring vs. raising) require to strike a balance.

Obviously, hiring &quot;only the top 1%&quot; means nothing when everybody &quot;hires top 1%&quot; (they aren't). Anon end others, how on earth do you think to hire &quot;only the best&quot; if everybody else does it? What happens with average developers? They switch profession? If so, suddenly your &quot;only the best&quot; people are average, aren't they?

Sorry, but your logic is flawed. Aanybody who says he &quot;hires only the best&quot; should take its head out of it's ... (Unless used as a marketing pitch, as Joel Spolsky brilliantly does).

On the other hand, growing internally and not looking outside may mean missing out, as well. It may be you can hire good people who were &quot;baked&quot; may just be easier than baking them yourself from existing pool (andm maybe even failing at that). Cutting off dead meat is good as well, if you can spot it (yes, it's hard). So, it's a question of balance.

See http://www.ericsink.com/articles/Choir.html. This one, IMO, hits it on the head. (Sink says there: &quot;I want to speak of team talent in terms of a choir.&quot;)</description>
		<content:encoded><![CDATA[	<p>Opposing forces (hiring vs. raising) require to strike a balance.</p>
	<p>Obviously, hiring &#8220;only the top 1%&#8221; means nothing when everybody &#8220;hires top 1%&#8221; (they aren&#8217;t). Anon end others, how on earth do you think to hire &#8220;only the best&#8221; if everybody else does it? What happens with average developers? They switch profession? If so, suddenly your &#8220;only the best&#8221; people are average, aren&#8217;t they?</p>
	<p>Sorry, but your logic is flawed. Aanybody who says he &#8220;hires only the best&#8221; should take its head out of it&#8217;s &#8230; (Unless used as a marketing pitch, as Joel Spolsky brilliantly does).</p>
	<p>On the other hand, growing internally and not looking outside may mean missing out, as well. It may be you can hire good people who were &#8220;baked&#8221; may just be easier than baking them yourself from existing pool (andm maybe even failing at that). Cutting off dead meat is good as well, if you can spot it (yes, it&#8217;s hard). So, it&#8217;s a question of balance.</p>
	<p>See <a href='http://www.ericsink.com/articles/Choir.html' rel='nofollow'>http://www.ericsink.com/articles/Choir.html</a>. This one, IMO, hits it on the head. (Sink says there: &#8220;I want to speak of team talent in terms of a choir.&#8221;)
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Hiring Great Developers? by: Mike-O-Matic &#187; You Can&#8217;t Grow A Redwood With Dandelion Seeds</title>
		<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2101</link>
		<pubDate>Wed, 04 Oct 2006 05:45:03 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2101</guid>
					<description>[...] Lidor over at The Mindset wrote a reaction article on just this topic. He asserts that companies should avoid drinking this punch, and instead focus on what they can do to raise the talent level of their current developers. People are the key to great software development. But people are not a commodity. They are… well, people. If you want a team of professionals, you can have one. But the only way to have more positions manned by professionals is to grow more professionals. [...]</description>
		<content:encoded><![CDATA[	<p>[&#8230;] Lidor over at The Mindset wrote a reaction article on just this topic. He asserts that companies should avoid drinking this punch, and instead focus on what they can do to raise the talent level of their current developers. People are the key to great software development. But people are not a commodity. They are… well, people. If you want a team of professionals, you can have one. But the only way to have more positions manned by professionals is to grow more professionals. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Hiring Great Developers? by: Blog de AlejoLp &#187; ¡¡No podía faltar!!</title>
		<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2096</link>
		<pubDate>Wed, 04 Oct 2006 03:12:32 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2096</guid>
					<description>[...] Hiring great developers? [...]</description>
		<content:encoded><![CDATA[	<p>[&#8230;] Hiring great developers? [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Hiring Great Developers? by: dennis</title>
		<link>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2089</link>
		<pubDate>Tue, 03 Oct 2006 18:28:37 +0000</pubDate>
		<guid>http://blog.qualityaspect.com/2006/10/02/hiring-great-developers/#comment-2089</guid>
					<description>What stats? Lines of code per day? I've noticed that the worse the developer, then longer the code. Bug count? One way to get a low bugcount is to avoid work. Number of fixed bugs? Poor developers start fixing a lot of trivial bugs to make the stats look good, while the good ones are spending days digging in to the hard ones.

Stats are worthless. Does the person deliver on hard projects, that's the only stat that matters.</description>
		<content:encoded><![CDATA[	<p>What stats? Lines of code per day? I&#8217;ve noticed that the worse the developer, then longer the code. Bug count? One way to get a low bugcount is to avoid work. Number of fixed bugs? Poor developers start fixing a lot of trivial bugs to make the stats look good, while the good ones are spending days digging in to the hard ones.</p>
	<p>Stats are worthless. Does the person deliver on hard projects, that&#8217;s the only stat that matters.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
