<?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"
	>
<channel>
	<title>Comments on: The Firepower of Teams</title>
	<atom:link href="http://www.hans-eric.com/2007/11/28/the-firepower-of-teams/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hans-eric.com/2007/11/28/the-firepower-of-teams/</link>
	<description>Hans-Eric Grönlund on software development</description>
	<pubDate>Mon, 08 Sep 2008 11:46:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Hans-Eric</title>
		<link>http://www.hans-eric.com/2007/11/28/the-firepower-of-teams/#comment-1208</link>
		<dc:creator>Hans-Eric</dc:creator>
		<pubDate>Fri, 30 Nov 2007 09:36:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/11/28/the-firepower-of-teams/#comment-1208</guid>
		<description>Good points. 
I too am mood-driven and sometimes on bleeding edge, sometimes in mainstream and sometimes legacy. It's equally fun as long as I'm getting somewhere, but I need to change tasks regularly to stay efficient.</description>
		<content:encoded><![CDATA[<p>Good points.<br />
I too am mood-driven and sometimes on bleeding edge, sometimes in mainstream and sometimes legacy. It&#8217;s equally fun as long as I&#8217;m getting somewhere, but I need to change tasks regularly to stay efficient.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans-Eric</title>
		<link>http://www.hans-eric.com/2007/11/28/the-firepower-of-teams/#comment-1207</link>
		<dc:creator>Hans-Eric</dc:creator>
		<pubDate>Fri, 30 Nov 2007 08:37:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/11/28/the-firepower-of-teams/#comment-1207</guid>
		<description>&lt;blockquote&gt;However, the generalization does hold overall: by and large, the best programmers will also be sufficiently interested in programming that they spend time out of work doing it, and contribute to open-source projects.&lt;/blockquote&gt;
Absolutely, but it depends a little on how you define "best". If you mean "most skilled", I agree. But if you mean "most productive" (from an employers point of view), then I'd say the generalization may or may not be true.</description>
		<content:encoded><![CDATA[<blockquote><p>However, the generalization does hold overall: by and large, the best programmers will also be sufficiently interested in programming that they spend time out of work doing it, and contribute to open-source projects.</p></blockquote>
<p>Absolutely, but it depends a little on how you define &#8220;best&#8221;. If you mean &#8220;most skilled&#8221;, I agree. But if you mean &#8220;most productive&#8221; (from an employers point of view), then I&#8217;d say the generalization may or may not be true.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul W. Homer</title>
		<link>http://www.hans-eric.com/2007/11/28/the-firepower-of-teams/#comment-1203</link>
		<dc:creator>Paul W. Homer</dc:creator>
		<pubDate>Thu, 29 Nov 2007 21:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/11/28/the-firepower-of-teams/#comment-1203</guid>
		<description>I think if you redefined it a bit to leaders and followers, it would be easier. Most programmers I know are a bit of each, and often that changes with age and whatever else is happening in their life. Sometimes I'm the first in, sometimes I wait, it often depends on how tired I am of banging my head against the brick wall of new technology.

The best programmers I know all share a common characteristic: they want to build things. They are driven deep inside by the need to create pieces of software. Not all of them 'care' about the technology or the vendor, instead they focus on what they want to create. Assembler, C, C++, Java, Cobol, RPG, APL, Lisp, etc. they are all just different means to the same ends. They all basically allow you to offer functionality to the user to manipulate data. Just because someone has a preference for some flashier bit of pain, doesn't make them any better or more sophisticated (in fact one might actually draw the opposite conclusion :-). It's all about the building.

It is the power and flexibility to create new tools or extend the existing ones that is important. If the capabilities are there, the actual technology is just a minor issue. 


Paul.</description>
		<content:encoded><![CDATA[<p>I think if you redefined it a bit to leaders and followers, it would be easier. Most programmers I know are a bit of each, and often that changes with age and whatever else is happening in their life. Sometimes I&#8217;m the first in, sometimes I wait, it often depends on how tired I am of banging my head against the brick wall of new technology.</p>
<p>The best programmers I know all share a common characteristic: they want to build things. They are driven deep inside by the need to create pieces of software. Not all of them &#8216;care&#8217; about the technology or the vendor, instead they focus on what they want to create. Assembler, C, C++, Java, Cobol, RPG, APL, Lisp, etc. they are all just different means to the same ends. They all basically allow you to offer functionality to the user to manipulate data. Just because someone has a preference for some flashier bit of pain, doesn&#8217;t make them any better or more sophisticated (in fact one might actually draw the opposite conclusion :-). It&#8217;s all about the building.</p>
<p>It is the power and flexibility to create new tools or extend the existing ones that is important. If the capabilities are there, the actual technology is just a minor issue. </p>
<p>Paul.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Williams</title>
		<link>http://www.hans-eric.com/2007/11/28/the-firepower-of-teams/#comment-1202</link>
		<dc:creator>Anthony Williams</dc:creator>
		<pubDate>Thu, 29 Nov 2007 17:07:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/2007/11/28/the-firepower-of-teams/#comment-1202</guid>
		<description>Ben's 80-20 generalization is just that: a generalization. Sure, there are programmers who know their company's software inside out, and can add three new features during a their coffee break, but only develop software when they're being paid, and only with the tools provided. There are also brilliant programmers who are too caught up in the bleeding edge technology that they don't manage to invest any energy in actually getting things done (rather than finding new ways to do it), and end up being thoroughly inefficient.

However, the generalization does hold overall: by and large, the best programmers will also be sufficiently interested in programming that they spend time out of work doing it, and contribute to open-source projects.

I wholeheartedly agree with your final comment, though: if we're working on a project (whether or not we're part of a team), it's important to focus on things that make progress towards the goals of the project, rather than just focusing on what we find interesting.</description>
		<content:encoded><![CDATA[<p>Ben&#8217;s 80-20 generalization is just that: a generalization. Sure, there are programmers who know their company&#8217;s software inside out, and can add three new features during a their coffee break, but only develop software when they&#8217;re being paid, and only with the tools provided. There are also brilliant programmers who are too caught up in the bleeding edge technology that they don&#8217;t manage to invest any energy in actually getting things done (rather than finding new ways to do it), and end up being thoroughly inefficient.</p>
<p>However, the generalization does hold overall: by and large, the best programmers will also be sufficiently interested in programming that they spend time out of work doing it, and contribute to open-source projects.</p>
<p>I wholeheartedly agree with your final comment, though: if we&#8217;re working on a project (whether or not we&#8217;re part of a team), it&#8217;s important to focus on things that make progress towards the goals of the project, rather than just focusing on what we find interesting.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.253 seconds -->
