<?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: Software Development as profession? Not Yet, Probably Never</title>
	<atom:link href="http://agilepainrelief.com/notesfromatooluser/2008/04/software-develo.html/feed" rel="self" type="application/rss+xml" />
	<link>http://agilepainrelief.com/notesfromatooluser/2008/04/software-develo.html</link>
	<description>Best practices for your goals</description>
	<lastBuildDate>Thu, 11 Mar 2010 23:31:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David White</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2008/04/software-develo.html/comment-page-1#comment-180</link>
		<dc:creator>David White</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2008/04/software-develo/#comment-180</guid>
		<description>I trained first as a mechanical engineer, working in the field for 16 years as a research engineer. At one stage I even managed to qualify as a Registered Engineer, which in NZ was the qualification to prove that I was worthy of joining the Institute of Professional Engineers here (though I never joined -- I regard myself as an &quot;uncivil engineer&quot;).

That experience left me with the view that &quot;professionals&quot; in that sense were overly elitist. Of course, it is financially self-centred for them to make entry into their &quot;club&quot; as difficult as possible, to minimise competition.

In contrast, the software industry seems to be far more open, with a greater encouragement to continuing education (perhaps because software technologies change more rapidly). I don&#039;t think that &quot;professionalism&quot; would necessarily calcify the development process.

In fact, I&#039;d credit the Agile community for raising the standards of software, by the emphasis on unit testing, and the better designs that result from coding for testability.

My view is that your development &quot;portfolio&quot; is the principle measure of your professionalism -- the projects that you were a part of, and the contribution that you made to them and their success (or otherwise).
</description>
		<content:encoded><![CDATA[<p>I trained first as a mechanical engineer, working in the field for 16 years as a research engineer. At one stage I even managed to qualify as a Registered Engineer, which in NZ was the qualification to prove that I was worthy of joining the Institute of Professional Engineers here (though I never joined &#8212; I regard myself as an &#8220;uncivil engineer&#8221;).</p>
<p>That experience left me with the view that &#8220;professionals&#8221; in that sense were overly elitist. Of course, it is financially self-centred for them to make entry into their &#8220;club&#8221; as difficult as possible, to minimise competition.</p>
<p>In contrast, the software industry seems to be far more open, with a greater encouragement to continuing education (perhaps because software technologies change more rapidly). I don&#8217;t think that &#8220;professionalism&#8221; would necessarily calcify the development process.</p>
<p>In fact, I&#8217;d credit the Agile community for raising the standards of software, by the emphasis on unit testing, and the better designs that result from coding for testability.</p>
<p>My view is that your development &#8220;portfolio&#8221; is the principle measure of your professionalism &#8212; the projects that you were a part of, and the contribution that you made to them and their success (or otherwise).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Wendelin</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2008/04/software-develo.html/comment-page-1#comment-181</link>
		<dc:creator>Eric Wendelin</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2008/04/software-develo/#comment-181</guid>
		<description>Not sure how things should go for &quot;professional&quot; software development. I would very much like quality of software projects to go up, but I agree that subscribing to one set of standards must not happen. If we are to move forward with this we would need to redefine how a profession works.
</description>
		<content:encoded><![CDATA[<p>Not sure how things should go for &#8220;professional&#8221; software development. I would very much like quality of software projects to go up, but I agree that subscribing to one set of standards must not happen. If we are to move forward with this we would need to redefine how a profession works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Software Development</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2008/04/software-develo.html/comment-page-1#comment-182</link>
		<dc:creator>Software Development</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2008/04/software-develo/#comment-182</guid>
		<description>Really It was an Interesting conversation! about the software. I was wondering here, is the software is the professional activity ? Hmm.....
</description>
		<content:encoded><![CDATA[<p>Really It was an Interesting conversation! about the software. I was wondering here, is the software is the professional activity ? Hmm&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: antonio</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2008/04/software-develo.html/comment-page-1#comment-183</link>
		<dc:creator>antonio</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2008/04/software-develo/#comment-183</guid>
		<description>I was discussing this with a good friend at work just the other day... software development has neither a code of ethics, really, nor a set of professional standards and practices. My friend blamed Microsoft (as the 800 pound gorilla that shaped the industry in the last 25 years) for lowering expectations. I think he&#039;s right but for a complicated reason: the hurdles developers have to go over have gone down, so it becomes much easier than it would otherwise be for someone to deliver enough value to earn a paycheck. It&#039;s much easier now than it was, say, 20 years ago to produce a program that more or less works and does something useful most of the time.

When I think about professionalization I think perhaps the way to come at it would be certification in different methodologies and technologies as they emerge, not an overall certification of &quot;Software Engineer&quot;.  Perhaps getting and keeping a &#039;developer license&#039; would require some combination of certs from a minimum number of methodologies and technologies, continuing education credits each year, etc.. &quot;You must do at least one dev technology course plus one architectural methods course plus one QA methodology course each three years to keep your license, but they can be focused on any of the following (long) list of technology vendors...&quot;

Not a perfect answer but one that at least makes possible the emergence of new methods and their integration into the world of &quot;acceptable&quot; practices.
</description>
		<content:encoded><![CDATA[<p>I was discussing this with a good friend at work just the other day&#8230; software development has neither a code of ethics, really, nor a set of professional standards and practices. My friend blamed Microsoft (as the 800 pound gorilla that shaped the industry in the last 25 years) for lowering expectations. I think he&#8217;s right but for a complicated reason: the hurdles developers have to go over have gone down, so it becomes much easier than it would otherwise be for someone to deliver enough value to earn a paycheck. It&#8217;s much easier now than it was, say, 20 years ago to produce a program that more or less works and does something useful most of the time.</p>
<p>When I think about professionalization I think perhaps the way to come at it would be certification in different methodologies and technologies as they emerge, not an overall certification of &#8220;Software Engineer&#8221;.  Perhaps getting and keeping a &#8216;developer license&#8217; would require some combination of certs from a minimum number of methodologies and technologies, continuing education credits each year, etc.. &#8220;You must do at least one dev technology course plus one architectural methods course plus one QA methodology course each three years to keep your license, but they can be focused on any of the following (long) list of technology vendors&#8230;&#8221;</p>
<p>Not a perfect answer but one that at least makes possible the emergence of new methods and their integration into the world of &#8220;acceptable&#8221; practices.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
