<?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: Business Value of Deep Understanding for Developers</title>
	<atom:link href="http://MarkFreedman.com/index.php/2007/08/19/business-value-of-deep-understanding-for-developers/feed/" rel="self" type="application/rss+xml" />
	<link>http://MarkFreedman.com/index.php/2007/08/19/business-value-of-deep-understanding-for-developers/</link>
	<description>Productivity through technology, and other related topics.</description>
	<pubDate>Wed, 08 Sep 2010 13:12:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Freedman</title>
		<link>http://MarkFreedman.com/index.php/2007/08/19/business-value-of-deep-understanding-for-developers/comment-page-1/#comment-199</link>
		<dc:creator>Mark Freedman</dc:creator>
		<pubDate>Sun, 13 Jan 2008 03:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://MarkFreedman.com/index.php/2007/08/19/business-value-of-deep-understanding-for-developers/#comment-199</guid>
		<description>Re-reading this now, I see your point.  In my company, this role has evolved into a combination PM / Architect role, and the PM role is a combination PM / Business Analyst role.  I may have been too close to it for almost eight years to recognize that both positions are sharing in the PM role.  That could also explain why I'm so often frustrated in my role there.  Never enough time to think.

Thanks for your comments.</description>
		<content:encoded><![CDATA[<p>Re-reading this now, I see your point.  In my company, this role has evolved into a combination PM / Architect role, and the PM role is a combination PM / Business Analyst role.  I may have been too close to it for almost eight years to recognize that both positions are sharing in the PM role.  That could also explain why I&#8217;m so often frustrated in my role there.  Never enough time to think.</p>
<p>Thanks for your comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RealWorldEngineer</title>
		<link>http://MarkFreedman.com/index.php/2007/08/19/business-value-of-deep-understanding-for-developers/comment-page-1/#comment-198</link>
		<dc:creator>RealWorldEngineer</dc:creator>
		<pubDate>Sat, 12 Jan 2008 00:22:50 +0000</pubDate>
		<guid isPermaLink="false">http://MarkFreedman.com/index.php/2007/08/19/business-value-of-deep-understanding-for-developers/#comment-198</guid>
		<description>Your definition of an architect seems to be a proxy for much of what a Project Manager should be responsible for.  In fact this definition sounds more like that in your company a lot of the work is getting pushed down or over onto the "architect" as a catch all position.

My philosophy is that an architect needs to be FOCUSED on the product or product line from the technology side.  The project manager should be responsible for process.

In a perfect world you would have --
  Engineering Manager: manages people first, process second, and technology third.
  Project Manager: manages process first and resources second.
  Architect: manages technology first, process second, and people third.

IMHO, the architect position is a thinking position and that requires time to think.</description>
		<content:encoded><![CDATA[<p>Your definition of an architect seems to be a proxy for much of what a Project Manager should be responsible for.  In fact this definition sounds more like that in your company a lot of the work is getting pushed down or over onto the &#8220;architect&#8221; as a catch all position.</p>
<p>My philosophy is that an architect needs to be FOCUSED on the product or product line from the technology side.  The project manager should be responsible for process.</p>
<p>In a perfect world you would have &#8211;<br />
  Engineering Manager: manages people first, process second, and technology third.<br />
  Project Manager: manages process first and resources second.<br />
  Architect: manages technology first, process second, and people third.</p>
<p>IMHO, the architect position is a thinking position and that requires time to think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amy B</title>
		<link>http://MarkFreedman.com/index.php/2007/08/19/business-value-of-deep-understanding-for-developers/comment-page-1/#comment-28</link>
		<dc:creator>Amy B</dc:creator>
		<pubDate>Thu, 23 Aug 2007 19:18:30 +0000</pubDate>
		<guid isPermaLink="false">http://MarkFreedman.com/index.php/2007/08/19/business-value-of-deep-understanding-for-developers/#comment-28</guid>
		<description>I think this goes far beyond the developer/architect realm.  I have been in organizations where the promotion from peon to Assistant Vice President and AVP to VP is considered the be-all or end-all.  Yet it means absolutely nothing in terms of pay, credibility or responsibility.  At one organization, 250 out of 2000 employees were AVPs, it's like water, it's so common.  Yet, 99% of the people I know were seriously disgruntled if they did not make AVP at 4 years and VP at 7, regardless of their performance (or more specifically, lack thereof!)  It's this sense of entitlement thing, I think.  Older generations didn't have it, but in the 30-somethings and younger, I definitely see it.</description>
		<content:encoded><![CDATA[<p>I think this goes far beyond the developer/architect realm.  I have been in organizations where the promotion from peon to Assistant Vice President and AVP to VP is considered the be-all or end-all.  Yet it means absolutely nothing in terms of pay, credibility or responsibility.  At one organization, 250 out of 2000 employees were AVPs, it&#8217;s like water, it&#8217;s so common.  Yet, 99% of the people I know were seriously disgruntled if they did not make AVP at 4 years and VP at 7, regardless of their performance (or more specifically, lack thereof!)  It&#8217;s this sense of entitlement thing, I think.  Older generations didn&#8217;t have it, but in the 30-somethings and younger, I definitely see it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
