<?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: Software Professionalism</title>
	<atom:link href="http://james.shade.org/blog/2007/05/03/software-professionalism/feed/" rel="self" type="application/rss+xml" />
	<link>http://james.shade.org/blog/2007/05/03/software-professionalism/</link>
	<description>Programming and other things</description>
	<pubDate>Wed, 19 Nov 2008 11:35:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Stephen Tjasink</title>
		<link>http://james.shade.org/blog/2007/05/03/software-professionalism/#comment-586</link>
		<dc:creator>Stephen Tjasink</dc:creator>
		<pubDate>Wed, 30 May 2007 14:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://james.shade.org/blog/2007/05/03/software-professionalism/#comment-586</guid>
		<description>This is a very important and complex topic.  The term "IT" is very broad, but ultimately everyone who is involved should be "brought into the fold" to some degree.  If project managers, account managers, line managers, helpdesk staff, etc, all have instilled in them a certain degree of professionalism and knowledge of the industry, then it makes it easier for software practitioners themselves.

And as to how we, as software practitioners, take control of our own industry, that is a difficult question.  When engineers "professionalised" their profession, were they working for companies who had salesmen that went out and sold projects that they were then expected to deliver ASAP without going over a very tight budget and not being allowed much thought towards the future?  These are things that impact professionalism in software development and can restrict activities that we would see as furthering professionalism.

It's going to be a tough struggle because of the nature of the modern commercial landscape.  We should not let that discourage us though and we should attempt to make useful gains wherever we can.</description>
		<content:encoded><![CDATA[<p>This is a very important and complex topic.  The term &#8220;IT&#8221; is very broad, but ultimately everyone who is involved should be &#8220;brought into the fold&#8221; to some degree.  If project managers, account managers, line managers, helpdesk staff, etc, all have instilled in them a certain degree of professionalism and knowledge of the industry, then it makes it easier for software practitioners themselves.</p>
<p>And as to how we, as software practitioners, take control of our own industry, that is a difficult question.  When engineers &#8220;professionalised&#8221; their profession, were they working for companies who had salesmen that went out and sold projects that they were then expected to deliver ASAP without going over a very tight budget and not being allowed much thought towards the future?  These are things that impact professionalism in software development and can restrict activities that we would see as furthering professionalism.</p>
<p>It&#8217;s going to be a tough struggle because of the nature of the modern commercial landscape.  We should not let that discourage us though and we should attempt to make useful gains wherever we can.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
