<?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: Why manage? when you can code!</title>
	<atom:link href="http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/</link>
	<description>Coffee Sessions for the Industry!</description>
	<lastBuildDate>Sat, 12 May 2012 08:39:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Who are more capable - Architects or Managers? : Green &#38; White</title>
		<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/comment-page-1/#comment-148670</link>
		<dc:creator>Who are more capable - Architects or Managers? : Green &#38; White</dc:creator>
		<pubDate>Wed, 21 Oct 2009 22:26:27 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/05/14/why-manage-when-you-can-code/#comment-148670</guid>
		<description>[...] content. Now, on with the regular content...One of the threads which branched off the previous post on software management was knowledge and breadth of the &#8216;manager&#8217; in the technology in [...]</description>
		<content:encoded><![CDATA[<p>[...] content. Now, on with the regular content&#8230;One of the threads which branched off the previous post on software management was knowledge and breadth of the &#8216;manager&#8217; in the technology in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adnan Siddiqi</title>
		<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/comment-page-1/#comment-11762</link>
		<dc:creator>Adnan Siddiqi</dc:creator>
		<pubDate>Mon, 19 May 2008 18:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/05/14/why-manage-when-you-can-code/#comment-11762</guid>
		<description>yaar Yasser I didn&#039;t mean a PM should be technology illetrate but then you can&#039;t expect a PM to give you solution that whether one should use jQuery or YUI or Flex.

I know in Pakistan having concept of application architect is not common since a PM is considered responsible(read culprit) for everything but in reality I would prefer to have a team of hard core developers(not Coders!),application architect,TL and a PM.</description>
		<content:encoded><![CDATA[<p>yaar Yasser I didn&#8217;t mean a PM should be technology illetrate but then you can&#8217;t expect a PM to give you solution that whether one should use jQuery or YUI or Flex.</p>
<p>I know in Pakistan having concept of application architect is not common since a PM is considered responsible(read culprit) for everything but in reality I would prefer to have a team of hard core developers(not Coders!),application architect,TL and a PM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yasser</title>
		<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/comment-page-1/#comment-11750</link>
		<dc:creator>Yasser</dc:creator>
		<pubDate>Mon, 19 May 2008 12:39:19 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/05/14/why-manage-when-you-can-code/#comment-11750</guid>
		<description>Adnan&#039;s point is valid and simply boils the discussion down to - who would you rather have as the manager of a team:

A) a technical architect
B) a manager with no technology know-how but only soft skills at his/her disposal.

I am obviously strongly biased towards A) based on my own experience.  But i understand and respect the fact that both of you would go for B).  It would make for a great study if you guys can find out examples of excellent non-technical managers who successfully led technology projects.  I have countless examples of managers in category A).</description>
		<content:encoded><![CDATA[<p>Adnan&#8217;s point is valid and simply boils the discussion down to &#8211; who would you rather have as the manager of a team:</p>
<p>A) a technical architect<br />
B) a manager with no technology know-how but only soft skills at his/her disposal.</p>
<p>I am obviously strongly biased towards A) based on my own experience.  But i understand and respect the fact that both of you would go for B).  It would make for a great study if you guys can find out examples of excellent non-technical managers who successfully led technology projects.  I have countless examples of managers in category A).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mansoor</title>
		<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/comment-page-1/#comment-11748</link>
		<dc:creator>mansoor</dc:creator>
		<pubDate>Mon, 19 May 2008 12:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/05/14/why-manage-when-you-can-code/#comment-11748</guid>
		<description>again, never thought i&#039;d say this but Adnan couldn&#039;t have put it any better!

this is what i was coming to as well, we&#039;re talking about managers, not architects. Domain experience and expertise is the domain of architects and analysts. their job is to ensure they can get all the requirements of the customer satisfied by the technological advancements available to them. however, it is not their jobs to manage the customer, manage their expectations, to manage schedule/time/cost triangle and so forth. 

when we couple both of these tasks onto one person, we get a decrease in productivity, because lets face it.. both of these are jobs which demand specific skillsets which are largely mutually exclusive.</description>
		<content:encoded><![CDATA[<p>again, never thought i&#8217;d say this but Adnan couldn&#8217;t have put it any better!</p>
<p>this is what i was coming to as well, we&#8217;re talking about managers, not architects. Domain experience and expertise is the domain of architects and analysts. their job is to ensure they can get all the requirements of the customer satisfied by the technological advancements available to them. however, it is not their jobs to manage the customer, manage their expectations, to manage schedule/time/cost triangle and so forth. </p>
<p>when we couple both of these tasks onto one person, we get a decrease in productivity, because lets face it.. both of these are jobs which demand specific skillsets which are largely mutually exclusive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adnan Siddiqi</title>
		<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/comment-page-1/#comment-11747</link>
		<dc:creator>Adnan Siddiqi</dc:creator>
		<pubDate>Mon, 19 May 2008 11:30:56 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/05/14/why-manage-when-you-can-code/#comment-11747</guid>
		<description>&lt;i&gt;as a manager i need to know what REST based web service
&lt;/i&gt;

I believe this is the job of application architect to figure out which technology should be used. It&#039;s not PM&#039;s headache to decide which technology would be best for certain product.</description>
		<content:encoded><![CDATA[<p><i>as a manager i need to know what REST based web service<br />
</i></p>
<p>I believe this is the job of application architect to figure out which technology should be used. It&#8217;s not PM&#8217;s headache to decide which technology would be best for certain product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yasser</title>
		<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/comment-page-1/#comment-11740</link>
		<dc:creator>Yasser</dc:creator>
		<pubDate>Mon, 19 May 2008 06:37:23 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/05/14/why-manage-when-you-can-code/#comment-11740</guid>
		<description>Knowing and practicing technology dont have to overlap. e.g. If my client wants to build a B2B service, as a manager i need to know what REST based web services do, what are their limitations and alternatives, irrespective of whether i have built a webservice myself or not.  

This is just my personal opinion but a non-technical manager can not effectively negotiate between the client and the developers if he doesn&#039;t know the technology involved.  

Google is the most successful software company of the last two decades and although it does encourage multi-disciplinary hiring, an absolute passion for the technology involved in creating google&#039;s products is one of the key requirements for new candidates.</description>
		<content:encoded><![CDATA[<p>Knowing and practicing technology dont have to overlap. e.g. If my client wants to build a B2B service, as a manager i need to know what REST based web services do, what are their limitations and alternatives, irrespective of whether i have built a webservice myself or not.  </p>
<p>This is just my personal opinion but a non-technical manager can not effectively negotiate between the client and the developers if he doesn&#8217;t know the technology involved.  </p>
<p>Google is the most successful software company of the last two decades and although it does encourage multi-disciplinary hiring, an absolute passion for the technology involved in creating google&#8217;s products is one of the key requirements for new candidates.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mansoor</title>
		<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/comment-page-1/#comment-11739</link>
		<dc:creator>mansoor</dc:creator>
		<pubDate>Mon, 19 May 2008 06:18:29 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/05/14/why-manage-when-you-can-code/#comment-11739</guid>
		<description>yasser: just one question, you said &quot;For managing technology projects, the manager needs to know the technology inside out irrespective of whether he practices it hands-on or not&quot;, 

tell me, if you have such a valuable resource who knows the technology inside out, wouldn&#039;t you rather have them implement that knowledge via coding or via system designing or would you rather  have them spend their time &#039;managing&#039; and thus making them more expensive?

one last thing, what exactly it is that technology-versed manager can do that a non-tech versed manager cant?</description>
		<content:encoded><![CDATA[<p>yasser: just one question, you said &#8220;For managing technology projects, the manager needs to know the technology inside out irrespective of whether he practices it hands-on or not&#8221;, </p>
<p>tell me, if you have such a valuable resource who knows the technology inside out, wouldn&#8217;t you rather have them implement that knowledge via coding or via system designing or would you rather  have them spend their time &#8216;managing&#8217; and thus making them more expensive?</p>
<p>one last thing, what exactly it is that technology-versed manager can do that a non-tech versed manager cant?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yasser</title>
		<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/comment-page-1/#comment-11691</link>
		<dc:creator>Yasser</dc:creator>
		<pubDate>Fri, 16 May 2008 10:16:55 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/05/14/why-manage-when-you-can-code/#comment-11691</guid>
		<description>I am all for having management people.  The point i was making was that the source of conflict between engineers and managers is NOT that engineers think managers are not important. That is not the case.  The dispute arises when the manager thinks he is &quot;above&quot; the team and the engineers think the manager is just playing an auxiliary role so he should not be rewarded more than the engineers. 

Also i have to disagree with your second observation as well.  &quot;People skills&quot; are necessary but not sufficient for being a good manager of technology.  HR management is the only place where people skills are necessary and sufficient.  For managing technology projects, the manager needs to know the technology inside out irrespective of whether he practices it hands-on or not.</description>
		<content:encoded><![CDATA[<p>I am all for having management people.  The point i was making was that the source of conflict between engineers and managers is NOT that engineers think managers are not important. That is not the case.  The dispute arises when the manager thinks he is &#8220;above&#8221; the team and the engineers think the manager is just playing an auxiliary role so he should not be rewarded more than the engineers. </p>
<p>Also i have to disagree with your second observation as well.  &#8220;People skills&#8221; are necessary but not sufficient for being a good manager of technology.  HR management is the only place where people skills are necessary and sufficient.  For managing technology projects, the manager needs to know the technology inside out irrespective of whether he practices it hands-on or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mansoor</title>
		<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/comment-page-1/#comment-11679</link>
		<dc:creator>mansoor</dc:creator>
		<pubDate>Fri, 16 May 2008 07:25:32 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/05/14/why-manage-when-you-can-code/#comment-11679</guid>
		<description>yasser: there&#039;s no denying that engineers are not important. however, the only venue of concern is, engineers are usually not interested in what a client wants, but rather how can they push the envelope of cutting technology technologies. also, since many engineers are also of high intellect, the comprehension that the general user will require only a few commands, and only those which get their work done instead of a whole bevy of &#039;cutting edge tools&#039; doesn&#039;t sit well with them. 

this is also an area of mediation where managers can play a role.. and also one reason why i believe atleast one manager should not be from a technical background at a software dev firm but rather from a people background.</description>
		<content:encoded><![CDATA[<p>yasser: there&#8217;s no denying that engineers are not important. however, the only venue of concern is, engineers are usually not interested in what a client wants, but rather how can they push the envelope of cutting technology technologies. also, since many engineers are also of high intellect, the comprehension that the general user will require only a few commands, and only those which get their work done instead of a whole bevy of &#8216;cutting edge tools&#8217; doesn&#8217;t sit well with them. </p>
<p>this is also an area of mediation where managers can play a role.. and also one reason why i believe atleast one manager should not be from a technical background at a software dev firm but rather from a people background.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yasser</title>
		<link>http://greenwhite.org/blog/2008/05/14/why-manage-when-you-can-code/comment-page-1/#comment-11648</link>
		<dc:creator>Yasser</dc:creator>
		<pubDate>Thu, 15 May 2008 10:33:59 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/05/14/why-manage-when-you-can-code/#comment-11648</guid>
		<description>Interesting point of view.  I dont think anyone denies the need for managing projects, even engineers know it in their hearts of hearts.  The real problem arises when the coders/engineers learn that their manager is making significantly more than they are; also when the manager starts thinking that because he is making more, his job is more important than that of the engineers.  A proportionate reward system and deserved appreciation of contribution, monetary and otherwise, an take care of the problem.  It can also help resist the temptation to become managers that most Pakistani engineers have.

In the most simplistic scenario imagine a team of 7 engineers with no manager. Can the team survive? May be!   Now imagine a team of 7 managers with no engineer ;-)</description>
		<content:encoded><![CDATA[<p>Interesting point of view.  I dont think anyone denies the need for managing projects, even engineers know it in their hearts of hearts.  The real problem arises when the coders/engineers learn that their manager is making significantly more than they are; also when the manager starts thinking that because he is making more, his job is more important than that of the engineers.  A proportionate reward system and deserved appreciation of contribution, monetary and otherwise, an take care of the problem.  It can also help resist the temptation to become managers that most Pakistani engineers have.</p>
<p>In the most simplistic scenario imagine a team of 7 engineers with no manager. Can the team survive? May be!   Now imagine a team of 7 managers with no engineer <img src='http://greenwhite.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

