<?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: Technical Leadership and People Management</title>
	<atom:link href="http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html</link>
	<description>Dealing with software projects in real life</description>
	<lastBuildDate>Fri, 10 Feb 2012 19:07:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html#comment-54766</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Wed, 25 Jan 2012 08:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2009/10/technical-leadership-and-people-management.html#comment-54766</guid>
		<description>@nikhil - I don&#039;t know where you work, but you should seriously consider changing the team. Or the job if that is how things look like in the whole organization.

I would say that you&#039;re wrong on so many levels but I won&#039;t as I know there are places such as the one you describe. BTW: if you feel like a prisoner you have two choices: either serve your sentence or escape :)</description>
		<content:encoded><![CDATA[<p>@nikhil &#8211; I don&#8217;t know where you work, but you should seriously consider changing the team. Or the job if that is how things look like in the whole organization.</p>
<p>I would say that you&#8217;re wrong on so many levels but I won&#8217;t as I know there are places such as the one you describe. BTW: if you feel like a prisoner you have two choices: either serve your sentence or escape :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nikhil</title>
		<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html#comment-54751</link>
		<dc:creator>nikhil</dc:creator>
		<pubDate>Wed, 25 Jan 2012 03:43:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2009/10/technical-leadership-and-people-management.html#comment-54751</guid>
		<description>Just as you mentioned one has to keep developing skills even if you get promoted in a group. This means you have to keep technical skills current to be able to lead your group. It is also a personal choice, if one just wants to be a manager or an employee or both. It also depends on one potential. Today economy is pressing huge demands on employees. However, employees are not receiving enough returns. Sure, it does build a good resume, but you also get trapped as a prisoner and often employers make sure you do not get any promotions. So off record you are so called lead! doing all managerial duties as well, while the real manager has no idea, since he has decided to pick the management of project track, which only involves meetings of which he has no idea what they are talking about in the meeting since he is now away from technical world as well.</description>
		<content:encoded><![CDATA[<p>Just as you mentioned one has to keep developing skills even if you get promoted in a group. This means you have to keep technical skills current to be able to lead your group. It is also a personal choice, if one just wants to be a manager or an employee or both. It also depends on one potential. Today economy is pressing huge demands on employees. However, employees are not receiving enough returns. Sure, it does build a good resume, but you also get trapped as a prisoner and often employers make sure you do not get any promotions. So off record you are so called lead! doing all managerial duties as well, while the real manager has no idea, since he has decided to pick the management of project track, which only involves meetings of which he has no idea what they are talking about in the meeting since he is now away from technical world as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html#comment-53035</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Thu, 05 Jan 2012 08:43:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2009/10/technical-leadership-and-people-management.html#comment-53035</guid>
		<description>@nikhil - Can&#039;t agree. Actually in terms of technical, hands-on, project-related experience I had basically none in every team I led since 2004. I had to choose: I could focus on learning new programming languages and keeping my technical sword sharp or focus on the thing I was paid for - managing people.

I made my choice and I don&#039;t feel like I was a bad manager.

Of course it is very different when you&#039;re promoted in a team you worked in for longer time so you get kick start basically for free. But even then, if you don&#039;t spend significant time actively sharpening your skills, they will be slowly but continuously disappearing.

If I was a great developer in 2003 (I wasn&#039;t but that&#039;s not the point) would I still be one now? No. Unless I kept actively working as one. If I spent, say, one third of my time as a developer would I still be great? A half, maybe? Now would I be able to become that much better manager over this time? No, not really. And believe me, I was a crappy manager back then.

I will give you the same challenge I gave Yogish - give me an example of someone who achieved this, someone who is widely considered both: a great developer and a great manager. If achieving that was easy I believe we should have truckload of such people.</description>
		<content:encoded><![CDATA[<p>@nikhil &#8211; Can&#8217;t agree. Actually in terms of technical, hands-on, project-related experience I had basically none in every team I led since 2004. I had to choose: I could focus on learning new programming languages and keeping my technical sword sharp or focus on the thing I was paid for &#8211; managing people.</p>
<p>I made my choice and I don&#8217;t feel like I was a bad manager.</p>
<p>Of course it is very different when you&#8217;re promoted in a team you worked in for longer time so you get kick start basically for free. But even then, if you don&#8217;t spend significant time actively sharpening your skills, they will be slowly but continuously disappearing.</p>
<p>If I was a great developer in 2003 (I wasn&#8217;t but that&#8217;s not the point) would I still be one now? No. Unless I kept actively working as one. If I spent, say, one third of my time as a developer would I still be great? A half, maybe? Now would I be able to become that much better manager over this time? No, not really. And believe me, I was a crappy manager back then.</p>
<p>I will give you the same challenge I gave Yogish &#8211; give me an example of someone who achieved this, someone who is widely considered both: a great developer and a great manager. If achieving that was easy I believe we should have truckload of such people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nikhil</title>
		<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html#comment-53021</link>
		<dc:creator>nikhil</dc:creator>
		<pubDate>Thu, 05 Jan 2012 04:48:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2009/10/technical-leadership-and-people-management.html#comment-53021</guid>
		<description>I agree with Yogish. However, companies are fearful of either loosing you for being too valuable or having to pay you more.
Also, how would you be a manager if you are not a part of the technical knowledge and projects?. It is never good for a manager to choose one or the other . A manager who picks and chooses is a bad manager.</description>
		<content:encoded><![CDATA[<p>I agree with Yogish. However, companies are fearful of either loosing you for being too valuable or having to pay you more.<br />
Also, how would you be a manager if you are not a part of the technical knowledge and projects?. It is never good for a manager to choose one or the other . A manager who picks and chooses is a bad manager.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html#comment-7441</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Wed, 07 Apr 2010 20:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2009/10/technical-leadership-and-people-management.html#comment-7441</guid>
		<description>Yogish,

Yes, being a manager doesn&#039;t automatically mean you &lt;i&gt;have to&lt;/i&gt; abandon technical track at all. But I keep my point that excellence in either one management or development takes too much time to be able to do both.

You may be average manager and great coder. You may be average coder and great manager. This actually mean you can do both, but there isn&#039;t much value of your average skill. It would probably be much better to focus on on your stronger side.

I can hardly imagine people who can excel in both areas but I don&#039;t say they don&#039;t exists. I&#039;d love to see an example. But even though they would be very, very rare.

I agree that management stereotypes don&#039;t help but that&#039;s not where is the source of the problem. Good manager would overcome organizational constraints in 9 cases out of 10. Heck, I saw multiple great teams built in companies which are basically hostile for healthy groups.

Personally I stopped tricking myself that I can catch on with technical track long ago. I see people trying to combine these two all the time and they&#039;re failing all the time and it happens in a wide range of different organizations. If someone finally succeeds, good for them, but I wouldn&#039;t bet with my own money.</description>
		<content:encoded><![CDATA[<p>Yogish,</p>
<p>Yes, being a manager doesn&#8217;t automatically mean you <i>have to</i> abandon technical track at all. But I keep my point that excellence in either one management or development takes too much time to be able to do both.</p>
<p>You may be average manager and great coder. You may be average coder and great manager. This actually mean you can do both, but there isn&#8217;t much value of your average skill. It would probably be much better to focus on on your stronger side.</p>
<p>I can hardly imagine people who can excel in both areas but I don&#8217;t say they don&#8217;t exists. I&#8217;d love to see an example. But even though they would be very, very rare.</p>
<p>I agree that management stereotypes don&#8217;t help but that&#8217;s not where is the source of the problem. Good manager would overcome organizational constraints in 9 cases out of 10. Heck, I saw multiple great teams built in companies which are basically hostile for healthy groups.</p>
<p>Personally I stopped tricking myself that I can catch on with technical track long ago. I see people trying to combine these two all the time and they&#8217;re failing all the time and it happens in a wide range of different organizations. If someone finally succeeds, good for them, but I wouldn&#8217;t bet with my own money.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yogish Baliga</title>
		<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html#comment-7423</link>
		<dc:creator>Yogish Baliga</dc:creator>
		<pubDate>Wed, 07 Apr 2010 19:47:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2009/10/technical-leadership-and-people-management.html#comment-7423</guid>
		<description>Being a manager does not necessarily mean you have to give up on technical track. You can be a hands-on coder, architect as well as manager at the same time. It is just a matter of time management. If one cannot do time management, he cannot be a good manager nor a good engineer. 

Yes.. In almost all the organization I have worked, what you say is correct. That is because all these policies are set by bunch of MBAs who don&#039;t want to think outside the box (what they learned). They think that what they learned is what they need to use.</description>
		<content:encoded><![CDATA[<p>Being a manager does not necessarily mean you have to give up on technical track. You can be a hands-on coder, architect as well as manager at the same time. It is just a matter of time management. If one cannot do time management, he cannot be a good manager nor a good engineer. </p>
<p>Yes.. In almost all the organization I have worked, what you say is correct. That is because all these policies are set by bunch of MBAs who don&#8217;t want to think outside the box (what they learned). They think that what they learned is what they need to use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vukoje</title>
		<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html#comment-3485</link>
		<dc:creator>Vukoje</dc:creator>
		<pubDate>Mon, 01 Feb 2010 20:12:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2009/10/technical-leadership-and-people-management.html#comment-3485</guid>
		<description>Thanks Pawel, I have a much clearer picture now. 
I think that the reason why I am under impression that I can do this is because I have really really good and close collaboration with my HR manager and Product Manager.</description>
		<content:encoded><![CDATA[<p>Thanks Pawel, I have a much clearer picture now.<br />
I think that the reason why I am under impression that I can do this is because I have really really good and close collaboration with my HR manager and Product Manager.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html#comment-3461</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Mon, 01 Feb 2010 09:08:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2009/10/technical-leadership-and-people-management.html#comment-3461</guid>
		<description>Yes, at least partially. If you avoid being a manager of a group (formally) you save a lot of time which you&#039;d spend on non-engineering-related tasks. If you want to make much use of your technical expertise make as much of your duties as possible engineering-related. This basically means you should prefer not to manage people directly.

But choosing to stay away from management also means you won&#039;t distribute tasks or motivate people (at least not the way most people consider it should be done).

From what you write I understand you have power to decide what exactly you&#039;re going to do. If I were you I&#039;d choose one side, either people management or technical leadership, and stick with it as much as possible. If your choice is technical leadership you can always switch to people management later. The other way around it&#039;s much harder.</description>
		<content:encoded><![CDATA[<p>Yes, at least partially. If you avoid being a manager of a group (formally) you save a lot of time which you&#8217;d spend on non-engineering-related tasks. If you want to make much use of your technical expertise make as much of your duties as possible engineering-related. This basically means you should prefer not to manage people directly.</p>
<p>But choosing to stay away from management also means you won&#8217;t distribute tasks or motivate people (at least not the way most people consider it should be done).</p>
<p>From what you write I understand you have power to decide what exactly you&#8217;re going to do. If I were you I&#8217;d choose one side, either people management or technical leadership, and stick with it as much as possible. If your choice is technical leadership you can always switch to people management later. The other way around it&#8217;s much harder.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vukoje</title>
		<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html#comment-3460</link>
		<dc:creator>Vukoje</dc:creator>
		<pubDate>Mon, 01 Feb 2010 08:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2009/10/technical-leadership-and-people-management.html#comment-3460</guid>
		<description>I was thinking more coaching, task distribution, code checking/testing, maybe motivation... not budgeting and reviews.

Does this make any difference in you opinion?</description>
		<content:encoded><![CDATA[<p>I was thinking more coaching, task distribution, code checking/testing, maybe motivation&#8230; not budgeting and reviews.</p>
<p>Does this make any difference in you opinion?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2009/10/technical-leadership-and-people.html#comment-3434</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Sun, 31 Jan 2010 14:20:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2009/10/technical-leadership-and-people-management.html#comment-3434</guid>
		<description>Vukoje,

If you look for a way to leverage knowledge and experience you shouldn&#039;t think about management but about technical leadership. This doesn&#039;t have to (and shouldn&#039;t if you ask me) be done through promoting a person to management position where he gets a team to supervise. You should rather think about all kind of guru roles, where a person has all the engineering tasks but is also a go-to guy when itcomes to technical advice or even decisions.

Call them tech leads, architects or whatever, but don&#039;t give them teams to manage since all these administrative tasks (like performance reviews, budgeting etc) steal a lot of time. Time which you could use either on coaching others or on engineering tasks.</description>
		<content:encoded><![CDATA[<p>Vukoje,</p>
<p>If you look for a way to leverage knowledge and experience you shouldn&#8217;t think about management but about technical leadership. This doesn&#8217;t have to (and shouldn&#8217;t if you ask me) be done through promoting a person to management position where he gets a team to supervise. You should rather think about all kind of guru roles, where a person has all the engineering tasks but is also a go-to guy when itcomes to technical advice or even decisions.</p>
<p>Call them tech leads, architects or whatever, but don&#8217;t give them teams to manage since all these administrative tasks (like performance reviews, budgeting etc) steal a lot of time. Time which you could use either on coaching others or on engineering tasks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

