<?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: Does generalising specialist mean you can&#8217;t be the best?</title>
	<atom:link href="http://www.markhneedham.com/blog/2008/08/11/does-generalising-specialist-mean-you-cant-be-the-best/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2008/08/11/does-generalising-specialist-mean-you-cant-be-the-best/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sat, 11 Feb 2012 23:17:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Kris Kemper</title>
		<link>http://www.markhneedham.com/blog/2008/08/11/does-generalising-specialist-mean-you-cant-be-the-best/comment-page-1/#comment-15</link>
		<dc:creator>Kris Kemper</dc:creator>
		<pubDate>Tue, 12 Aug 2008 03:09:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=55#comment-15</guid>
		<description>I guess it all depends on what you mean by the &quot;best.&quot; Will you likely sacrificing some productivity by being a generalist? Probably - If only because you don&#039;t have all the minute details on the edge of your memory when you move around to different languages.

However, I think this is more due to the fact that you generally don&#039;t use Java and C# at the same time - you use one or the other for months or years at a time, which causes you to rust in the one you&#039;re not active in.

A consequence of specialization is that you need more initial people to complete an entire project. Then, you need a redundant extra number of people in their specialty to mitigate the risk of something happening to someone. It&#039;s feasible for large companies to do this, even if it probably isn&#039;t efficient. To a small company however, one person (or a few) that can do a little bit of every job well is critical.</description>
		<content:encoded><![CDATA[<p>I guess it all depends on what you mean by the &#8220;best.&#8221; Will you likely sacrificing some productivity by being a generalist? Probably &#8211; If only because you don&#8217;t have all the minute details on the edge of your memory when you move around to different languages.</p>
<p>However, I think this is more due to the fact that you generally don&#8217;t use Java and C# at the same time &#8211; you use one or the other for months or years at a time, which causes you to rust in the one you&#8217;re not active in.</p>
<p>A consequence of specialization is that you need more initial people to complete an entire project. Then, you need a redundant extra number of people in their specialty to mitigate the risk of something happening to someone. It&#8217;s feasible for large companies to do this, even if it probably isn&#8217;t efficient. To a small company however, one person (or a few) that can do a little bit of every job well is critical.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

