<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: The Programmer is Dead; Long Live the Developer!</title>
	<atom:link href="http://enfranchisedmind.com/blog/posts/the-programmer-is-dead-long-live-the-developer/feed/" rel="self" type="application/rss+xml" />
	<link>http://enfranchisedmind.com/blog/posts/the-programmer-is-dead-long-live-the-developer/</link>
	<description>programming, politics, &#38; other religious issues</description>
	<lastBuildDate>Wed, 08 Feb 2012 14:16:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Enfranchised Mind &#187; We Aren&#8217;t Too Stupid for Polyglot Programming</title>
		<link>http://enfranchisedmind.com/blog/posts/the-programmer-is-dead-long-live-the-developer/#comment-36666</link>
		<dc:creator>Enfranchised Mind &#187; We Aren&#8217;t Too Stupid for Polyglot Programming</dc:creator>
		<pubDate>Fri, 07 Aug 2009 15:39:38 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/?p=41#comment-36666</guid>
		<description>[...] of software development has transitioned in large swaths of the industry. As I noted in my ancient The Programmer is Dead; Long Live the Developer! post, actual computer programming is often not the part of the job that pays the bills. The part of [...]</description>
		<content:encoded><![CDATA[<p>[...] of software development has transitioned in large swaths of the industry. As I noted in my ancient The Programmer is Dead; Long Live the Developer! post, actual computer programming is often not the part of the job that pays the bills. The part of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why Your Programming Language Is &#8220;Too Academic&#8221; &#124; Enfranchised Mind</title>
		<link>http://enfranchisedmind.com/blog/posts/the-programmer-is-dead-long-live-the-developer/#comment-34420</link>
		<dc:creator>Why Your Programming Language Is &#8220;Too Academic&#8221; &#124; Enfranchised Mind</dc:creator>
		<pubDate>Sun, 19 Apr 2009 02:24:47 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/?p=41#comment-34420</guid>
		<description>[...] More on programmer-technicians over at The Programmer is Dead; Long Live the Developer!, a post which has proven itself more and more accurate with the rise of CMSes (including [...]</description>
		<content:encoded><![CDATA[<p>[...] More on programmer-technicians over at The Programmer is Dead; Long Live the Developer!, a post which has proven itself more and more accurate with the rise of CMSes (including [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Fischer</title>
		<link>http://enfranchisedmind.com/blog/posts/the-programmer-is-dead-long-live-the-developer/#comment-33621</link>
		<dc:creator>Robert Fischer</dc:creator>
		<pubDate>Sun, 03 Aug 2008 15:42:11 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/?p=41#comment-33621</guid>
		<description>What&#039;s your definition of &quot;the long term&quot;?

&lt;div style=&quot;width:540px&quot;&gt;
&lt;a href=&quot;http://www.indeed.com/jobtrends?q=cobol%2C+perl%2C+java%2C+C%2B%2B&quot; title=&quot;cobol, perl, java, C++ Job Trends&quot; rel=&quot;nofollow&quot;&gt;
&lt;img width=&quot;540&quot; height=&quot;300&quot; src=&quot;http://www.indeed.com/trendgraph/jobgraph.png?q=cobol%2C+perl%2C+java%2C+C%2B%2B&quot; border=&quot;0&quot; alt=&quot;cobol, perl, java, C++ Job Trends graph&quot;&gt;
&lt;/a&gt;
&lt;table width=&quot;100%&quot; cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;0&quot; style=&quot;font-size:80%&quot;&gt;&lt;tr&gt;
&lt;td&gt;&lt;a href=&quot;http://www.indeed.com/jobtrends?q=cobol%2C+perl%2C+java%2C+C%2B%2B&quot; rel=&quot;nofollow&quot;&gt;cobol, perl, java, C++ Job Trends&lt;/a&gt;&lt;/td&gt;
&lt;td align=&quot;right&quot;&gt;&lt;a href=&quot;http://www.indeed.com/jobs?q=cobol&quot; rel=&quot;nofollow&quot;&gt;cobol jobs&lt;/a&gt; - &lt;a href=&quot;http://www.indeed.com/jobs?q=perl&quot; rel=&quot;nofollow&quot;&gt;perl jobs&lt;/a&gt; - &lt;a href=&quot;http://www.indeed.com/jobs?q=java&quot; rel=&quot;nofollow&quot;&gt;java jobs&lt;/a&gt; - &lt;a href=&quot;http://www.indeed.com/jobs?q=C%2B%2B&quot; rel=&quot;nofollow&quot;&gt;C++ jobs&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;

So far, there&#039;s still a solid market for COBOL, Perl, and C++ jobs: I&#039;m not sure you get much &quot;longer term&quot; in the programming word.  Growth is certainly dropping off, but if you went into the market learning COBOL, you&#039;re pushing firmly into retirement age at this point.

The problem is that while the &lt;em&gt;industry&lt;/em&gt; may be evolving, many companies aren&#039;t.  And companies want interoperable parts.  They don&#039;t want to pay someone who is going to have to come in and learn how to operate Eclipse or Visual Studio or Hibernate/NHibernate or whatever.  They want someone who can hit the ground running with the technologies they are using now.

To this extent, someone who knows many languages somewhat is providing a much poorer service than someone who knows one language and its tools well -- think about the level of expertise required to masterfully handle Seam or Rails.  You could (and many people do) spend full-time chasing after the &quot;bleeding edge&quot; of Ruby/Rails or Groovy/Grails, and for clients using those technologies, that is a very important skill.

The role of a polyglot is limited to experimental teams, either in start-ups or in experimental (and often politically risky) projects within larger corporations.  From a project manager&#039;s/business owner&#039;s standpoint, a new technology is only justifiable if it gains a value greater than the cost of retraining the team and taking the initial productivity hit -- and usually that&#039;s measured between now and the 1.0 release, because most projects don&#039;t get past that point.  In that kind of limited scope, it&#039;s very hard to justify a new technology as relevant or valuable.

And that&#039;s how new technologies get added onto the &quot;to try out&quot; list, and never get off.</description>
		<content:encoded><![CDATA[<p>What&#8217;s your definition of &#8220;the long term&#8221;?</p>
<div style="width:540px">
<a href="http://www.indeed.com/jobtrends?q=cobol%2C+perl%2C+java%2C+C%2B%2B" title="cobol, perl, java, C++ Job Trends" rel="nofollow"><br />
<img width="540" height="300" src="http://www.indeed.com/trendgraph/jobgraph.png?q=cobol%2C+perl%2C+java%2C+C%2B%2B" border="0" alt="cobol, perl, java, C++ Job Trends graph"/><br />
</a></p>
<table width="100%" cellpadding="6" cellspacing="0" border="0" style="font-size:80%">
<tr>
<td><a href="http://www.indeed.com/jobtrends?q=cobol%2C+perl%2C+java%2C+C%2B%2B" rel="nofollow">cobol, perl, java, C++ Job Trends</a></td>
<td align="right"><a href="http://www.indeed.com/jobs?q=cobol" rel="nofollow">cobol jobs</a> &#8211; <a href="http://www.indeed.com/jobs?q=perl" rel="nofollow">perl jobs</a> &#8211; <a href="http://www.indeed.com/jobs?q=java" rel="nofollow">java jobs</a> &#8211; <a href="http://www.indeed.com/jobs?q=C%2B%2B" rel="nofollow">C++ jobs</a></td>
</tr>
</table>
</div>
<p>So far, there&#8217;s still a solid market for COBOL, Perl, and C++ jobs: I&#8217;m not sure you get much &#8220;longer term&#8221; in the programming word.  Growth is certainly dropping off, but if you went into the market learning COBOL, you&#8217;re pushing firmly into retirement age at this point.</p>
<p>The problem is that while the <em>industry</em> may be evolving, many companies aren&#8217;t.  And companies want interoperable parts.  They don&#8217;t want to pay someone who is going to have to come in and learn how to operate Eclipse or Visual Studio or Hibernate/NHibernate or whatever.  They want someone who can hit the ground running with the technologies they are using now.</p>
<p>To this extent, someone who knows many languages somewhat is providing a much poorer service than someone who knows one language and its tools well &#8212; think about the level of expertise required to masterfully handle Seam or Rails.  You could (and many people do) spend full-time chasing after the &#8220;bleeding edge&#8221; of Ruby/Rails or Groovy/Grails, and for clients using those technologies, that is a very important skill.</p>
<p>The role of a polyglot is limited to experimental teams, either in start-ups or in experimental (and often politically risky) projects within larger corporations.  From a project manager&#8217;s/business owner&#8217;s standpoint, a new technology is only justifiable if it gains a value greater than the cost of retraining the team and taking the initial productivity hit &#8212; and usually that&#8217;s measured between now and the 1.0 release, because most projects don&#8217;t get past that point.  In that kind of limited scope, it&#8217;s very hard to justify a new technology as relevant or valuable.</p>
<p>And that&#8217;s how new technologies get added onto the &#8220;to try out&#8221; list, and never get off.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamlet D\'Arcy</title>
		<link>http://enfranchisedmind.com/blog/posts/the-programmer-is-dead-long-live-the-developer/#comment-33620</link>
		<dc:creator>Hamlet D\'Arcy</dc:creator>
		<pubDate>Fri, 01 Aug 2008 18:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/?p=41#comment-33620</guid>
		<description>It&#039;s not so much the &quot;computer revolution&quot; that changed how (and by whom) work was performed. In broader terms, the service industry revolution is responsible, and will most likely be the successor of the Industrial Revolution in history books of the future. 

Software engineers make their living providing a service. If the service you provide is poor then you can be replaced easily. If the service is high quality then you cannot. Waiters at restaurants are the same way. It is not easy to find a waiter for high end restaurants because most wait staff will not provide your customers with the same level of quality as you expect. In the same way, high end engineers are hard to find because most engineers produce work that is vastly inferior to that of the high end. 

As for the single-technology-stack developers... I see two distinct questions with two distinct answers: 

1) Will there always be jobs for these people? Yes. Absolutely. 
2) Will there be a future for these people? No. Absolutely not. 

When the industry stops and quits evolving is the day that investing in a single technology stack will pay dividends. In the meantime, for most it is a single investment that will pay diminishing returns in the long term.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not so much the &#8220;computer revolution&#8221; that changed how (and by whom) work was performed. In broader terms, the service industry revolution is responsible, and will most likely be the successor of the Industrial Revolution in history books of the future. </p>
<p>Software engineers make their living providing a service. If the service you provide is poor then you can be replaced easily. If the service is high quality then you cannot. Waiters at restaurants are the same way. It is not easy to find a waiter for high end restaurants because most wait staff will not provide your customers with the same level of quality as you expect. In the same way, high end engineers are hard to find because most engineers produce work that is vastly inferior to that of the high end. </p>
<p>As for the single-technology-stack developers&#8230; I see two distinct questions with two distinct answers: </p>
<p>1) Will there always be jobs for these people? Yes. Absolutely.<br />
2) Will there be a future for these people? No. Absolutely not. </p>
<p>When the industry stops and quits evolving is the day that investing in a single technology stack will pay dividends. In the meantime, for most it is a single investment that will pay diminishing returns in the long term.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Fischer</title>
		<link>http://enfranchisedmind.com/blog/posts/the-programmer-is-dead-long-live-the-developer/#comment-32462</link>
		<dc:creator>Robert Fischer</dc:creator>
		<pubDate>Mon, 28 Jan 2008 21:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/?p=41#comment-32462</guid>
		<description>BTW, I&#039;m Candide.</description>
		<content:encoded><![CDATA[<p>BTW, I&#8217;m Candide.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

