<?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: Hacker or Developer?</title>
	<atom:link href="http://www.hans-eric.com/2008/07/29/123/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hans-eric.com/2008/07/29/123/</link>
	<description>Hans-Eric Grönlund on software development</description>
	<pubDate>Wed, 07 Jan 2009 11:47:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Alastair Revell</title>
		<link>http://www.hans-eric.com/2008/07/29/123/#comment-13699</link>
		<dc:creator>Alastair Revell</dc:creator>
		<pubDate>Sat, 09 Aug 2008 02:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/?p=123#comment-13699</guid>
		<description>I think the distinction between those that do (1) and those that do (2) basically comes down to professionalism, which is something that is often in short supply in our industry - or should that be profession?


Alastair Revell
Managing Consultant
&lt;a href="http://www.rrs.co.uk" rel="nofollow"&gt;Revell Research Systems&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I think the distinction between those that do (1) and those that do (2) basically comes down to professionalism, which is something that is often in short supply in our industry - or should that be profession?</p>
<p>Alastair Revell<br />
Managing Consultant<br />
<a href="http://www.rrs.co.uk" rel="nofollow">Revell Research Systems</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans-Eric</title>
		<link>http://www.hans-eric.com/2008/07/29/123/#comment-13097</link>
		<dc:creator>Hans-Eric</dc:creator>
		<pubDate>Tue, 29 Jul 2008 15:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/?p=123#comment-13097</guid>
		<description>Hi Paul,

I like your definitions.

There are several terminologies with loose or changing definitions out there: software engineers, interaction engineers, implementation engineers, developers, programmers, various types of analysts, hackers, hci experts, you name it.

But then again, it doesn't really matter what we choose to call ourselves. It's what we do that matters, and I think Jeff's blog post highlights that in a nice way.</description>
		<content:encoded><![CDATA[<p>Hi Paul,</p>
<p>I like your definitions.</p>
<p>There are several terminologies with loose or changing definitions out there: software engineers, interaction engineers, implementation engineers, developers, programmers, various types of analysts, hackers, hci experts, you name it.</p>
<p>But then again, it doesn&#8217;t really matter what we choose to call ourselves. It&#8217;s what we do that matters, and I think Jeff&#8217;s blog post highlights that in a nice way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul W. Homer</title>
		<link>http://www.hans-eric.com/2008/07/29/123/#comment-13092</link>
		<dc:creator>Paul W. Homer</dc:creator>
		<pubDate>Tue, 29 Jul 2008 14:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.hans-eric.com/?p=123#comment-13092</guid>
		<description>For terminology I like using 'programmer' for the people that are 'just' coding, and 'developer' for the others that are working the full spectrum from analysis, design, implementation and deployment. It takes a huge number of diverse skills to be able to bring a big product or system together.

For a while the term 'business analysis' was popular, defined as someone dedicated towards grabbing the business requirements. It died out because they tended towards hiring people without programming backgrounds. That didn't work because they may get access to the one side, business, but they don't understand how to turn that into the other, code. If as an analyst, you don't know what you are looking for, you'll waste a lot of time.

Paul.</description>
		<content:encoded><![CDATA[<p>For terminology I like using &#8216;programmer&#8217; for the people that are &#8216;just&#8217; coding, and &#8216;developer&#8217; for the others that are working the full spectrum from analysis, design, implementation and deployment. It takes a huge number of diverse skills to be able to bring a big product or system together.</p>
<p>For a while the term &#8216;business analysis&#8217; was popular, defined as someone dedicated towards grabbing the business requirements. It died out because they tended towards hiring people without programming backgrounds. That didn&#8217;t work because they may get access to the one side, business, but they don&#8217;t understand how to turn that into the other, code. If as an analyst, you don&#8217;t know what you are looking for, you&#8217;ll waste a lot of time.</p>
<p>Paul.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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