<?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: The 18 Mistakes That Kill Startups</title>
	<atom:link href="http://www.integrativestream.com/2007/03/11/the-18-mistakes-that-kill-startups.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.integrativestream.com/2007/03/11/the-18-mistakes-that-kill-startups.html</link>
	<description>Disrupting Innovation since 2002</description>
	<lastBuildDate>Mon, 24 Dec 2007 12:57:52 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John</title>
		<link>http://www.integrativestream.com/2007/03/11/the-18-mistakes-that-kill-startups.html/comment-page-1#comment-26367</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 12 Mar 2007 01:54:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.integrativestream.com/2007/03/11/the-18-mistakes-that-kill-startups.html#comment-26367</guid>
		<description>Paul Graham&#039;s story is correct, but he&#039;s emphasizing the wrong part: It&#039;s not hiring bad programmers, it&#039;s business leaders in high tech who just don&#039;t know enough about the software development process or the special problems of hiring techies. I.e., the title just can&#039;t be &quot;hiring bad programmers&quot;: That&#039;s the symptom not the disease.

[And one could be the question in the first place: &quot;bad&quot;? What an empty word.]

When he says: &quot;I was about to say youâ€™d have to find a good programmer to help you hire people. But if you canâ€™t recognize good programmers, how would you even do that?&quot;

Answer: Find a business/tech hybrid who has done it before. (Someone like Will Crawford, perhaps.)

The big answer is about the impedance mismatch between business knowledge and technology knowledge. That&#039;s the hard one. You might almost want to rephrase the mistake as: &quot;Ignore the knowledge impedance between business process and technology process.&quot;</description>
		<content:encoded><![CDATA[<p>Paul Graham&#8217;s story is correct, but he&#8217;s emphasizing the wrong part: It&#8217;s not hiring bad programmers, it&#8217;s business leaders in high tech who just don&#8217;t know enough about the software development process or the special problems of hiring techies. I.e., the title just can&#8217;t be &#8220;hiring bad programmers&#8221;: That&#8217;s the symptom not the disease.</p>
<p>[And one could be the question in the first place: "bad"? What an empty word.]</p>
<p>When he says: &#8220;I was about to say youâ€™d have to find a good programmer to help you hire people. But if you canâ€™t recognize good programmers, how would you even do that?&#8221;</p>
<p>Answer: Find a business/tech hybrid who has done it before. (Someone like Will Crawford, perhaps.)</p>
<p>The big answer is about the impedance mismatch between business knowledge and technology knowledge. That&#8217;s the hard one. You might almost want to rephrase the mistake as: &#8220;Ignore the knowledge impedance between business process and technology process.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
