<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Eric D. Brown &#187; specialist</title>
	<atom:link href="http://ericbrown.com/tag/specialist/feed/" rel="self" type="application/rss+xml" />
	<link>http://ericbrown.com</link>
	<description>Technology, Strategy, People and Projects</description>
	<lastBuildDate>Tue, 22 May 2012 18:46:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Tyner Blain &#8211; “Specializing Generalists’</title>
		<link>http://ericbrown.com/specializing-generalists.htm?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=specializing-generalists</link>
		<comments>http://ericbrown.com/specializing-generalists.htm#comments</comments>
		<pubDate>Sun, 17 Feb 2008 00:51:32 +0000</pubDate>
		<dc:creator>Eric D. Brown</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[expert]]></category>
		<category><![CDATA[generalist]]></category>
		<category><![CDATA[specialist]]></category>

		<guid isPermaLink="false">http://ericbrown.com/specializing-generalists.htm</guid>
		<description><![CDATA[I just read an interesting article at Tyner Blain titled &#8220;Specializing Generalists and the Politics of Agile&#8220;that is a good follow up to my &#8220;Better to be a Generalist or Expert?&#8220;article. An excerpt is: By staffing a team with people who have an area of expertise, but can do anything, you can maximize the value [...]]]></description>
			<content:encoded><![CDATA[<p>I just read an interesting article at Tyner Blain titled &#8220;<a target="_blank" href="http://tynerblain.com/blog/2008/02/14/specializing-generalists/">Specializing Generalists and the Politics of Agile</a>&#8220;that is a good follow up to my &#8220;<a href="http://ericbrown.com/better-to-be-a-generalist-or-expert.htm">Better to be a Generalist or Expert?</a>&#8220;article.  An excerpt is:</p>
<blockquote><p>By staffing a team with people who have an area of expertise, but can do anything, you can maximize the value of each delivery cycle. In our example, where all of the tasks for a release are UI tasks, they can be interchangeably assigned to any of the developers. The UI expert may suggest an implementation approach, do code reviews, or provide guidance to all the other developers. But every developer (including the database guy) can sling code <em>effectively</em> to get the job done.  Specializing generalists.</p></blockquote>
<p>Go read the article&#8230;very interesting.</p>
<p>[tags]  Expert,  Generalist,  Specialist [/tags] </p>
]]></content:encoded>
			<wfw:commentRss>http://ericbrown.com/specializing-generalists.htm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Better to be a Generalist or Expert?</title>
		<link>http://ericbrown.com/better-to-be-a-generalist-or-expert.htm?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=better-to-be-a-generalist-or-expert</link>
		<comments>http://ericbrown.com/better-to-be-a-generalist-or-expert.htm#comments</comments>
		<pubDate>Tue, 29 Jan 2008 11:28:47 +0000</pubDate>
		<dc:creator>Eric D. Brown</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Misc]]></category>
		<category><![CDATA[expert]]></category>
		<category><![CDATA[generalist]]></category>
		<category><![CDATA[specialist]]></category>

		<guid isPermaLink="false">http://ericbrown.com/better-to-be-a-generalist-or-expert.htm</guid>
		<description><![CDATA[It seems like I&#8217;ve had this discussion recently with quite a few people&#8230;not sure if its because I like the topic or if lots of other people like it to. Basically, the conversation comes down to this short question: Is it better to be an expert (aka specialist) or generalist? Personally, I think it&#8217;s better [...]]]></description>
			<content:encoded><![CDATA[<p>It seems like I&#8217;ve had this discussion recently with quite a few people&#8230;not sure if its because I like the topic or if lots of other people like it to.</p>
<p>Basically, the conversation comes down to this short question:</p>
<blockquote><p><em>Is it better to be an expert (aka specialist) or generalist? </em></p></blockquote>
<p>Personally, I think it&#8217;s better to be a generalist with deep knowledge in a few areas and a much broader knowledge base in multiple industries and functional areas.  My areas of interest are so broad that I&#8217;ll never be an expert in anything&#8230;but I do have a deep understanding of a few functional areas (Technology, Project Management, Business Management) and a broader knowledge base in others (Marketing, Training, IT Operations, etc).</p>
<p>That said, there is a need for experts in all areas.  For example, I&#8217;m not sure you&#8217;d want a &#8216;generalist&#8217; as your technical architect, database administrator or brain surgeon.  These are areas where you would want to be an expert&#8230;but these are also areas that attract people who want to be experts.  You wouldn&#8217;t want me designing the technical architecture of a new enterprise level system&#8230;you&#8217;d want someone involved that truly understood all facets of the system to be designed and the environment it will operate in.</p>
<p>A few interesting articles/blog posts on this topic can be found below.</p>
<ul>
<li><a target="_blank" href="http://infosecplace.com/blog/2006/11/18/generalist-vs-expert/">Generalist vs. Expert</a> &#8211; Blog post about this topic within the Information Security field</li>
<li><a target="_blank" href="http://www.developerdotstar.com/community/node/45">To specialize or generalize?</a> &#8211; Question/Post about specializing or generalizing in the Software Field.</li>
<li><a target="_blank" href="http://www.ddj.com/architect/184415788">Agile Developer: Generalists or Specialists</a> &#8211; Argues that generalists are better.</li>
<li><a target="_blank" href="http://bellcr.com/?p=204">Death of the Generalist</a> &#8211; The topic from a Design standpoint.  Great article.</li>
</ul>
<p>After the many discussions, I&#8217;ve come to the conclusion that neither is better than the other. There&#8217;s room for experts/specialists and generalists in all fields.  What&#8217;s your thoughts on the subject?</p>
<p>[tags] Expert, Generalist, Specialist [/tags] </p>
]]></content:encoded>
			<wfw:commentRss>http://ericbrown.com/better-to-be-a-generalist-or-expert.htm/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using apc
Database Caching 3/7 queries in 0.002 seconds using apc
Object Caching 678/679 objects using apc
Content Delivery Network via Amazon Web Services: CloudFront: files.ericbrown.com

Served from: ericbrown.com @ 2012-05-25 00:15:17 -->
