<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>mattwalters.net &#187; How-To</title>
	<atom:link href="http://mattwalters.net/topic/how-to/feed/" rel="self" type="application/rss+xml" />
	<link>http://mattwalters.net</link>
	<description></description>
	<pubDate>Thu, 26 Jun 2008 03:01:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<item>
		<title>Management and Geeks</title>
		<link>http://mattwalters.net/2006/05/27/management-and-geeks/</link>
		<comments>http://mattwalters.net/2006/05/27/management-and-geeks/#comments</comments>
		<pubDate>Sat, 27 May 2006 06:59:44 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
		
		<category><![CDATA[How-To]]></category>

		<category><![CDATA[Reviews]]></category>

		<guid isPermaLink="false">http://mattwalters.net/blog/permalink/42/</guid>
		<description><![CDATA[A couple of days ago a coworker shared a link to a blog post about how not to manage geeks with me.  Then recently I saw it turn up on Digg.  I took a few moments to respond to him with what I thought in regards to the points, and thought that I [...]]]></description>
			<content:encoded><![CDATA[<p>A couple of days ago a coworker shared a link to a <a href="http://positivesharing.com/2006/03/how-not-to-lead-geeks/" rel="external">blog post about how not to manage geeks</a> with me.  Then recently I saw it turn up on Digg.  I took a few moments to respond to him with what I thought in regards to the points, and thought that I might share those here as well.  I&#8217;m not going to quote EVERYTHING from the original post, so I recommend you go over and read it to see the explanation that was placed with each of these points before reading my responses below.</p>
<blockquote><p>1: Downplay training</p></blockquote>
<p>Eh &#8230; I don&#8217;t mind teaching myself stuff.  I actually learn better this way.  I&#8217;m willing to admit that I might very well be an exception on this though.</p>
<blockquote><p>2: Give no recognition</p></blockquote>
<p>Definitely important.  I personally don&#8217;t need public recognition as much as just an occasional, &#8220;Hey, that was pretty sweet how you did x&#8221;</p>
<blockquote><p>3: Plan too much overtime</p></blockquote>
<p>Obviously this is bad.  Bad as in planning overtime is bad, not as in the point is bad.</p>
<blockquote><p>4: Use management-speak</p></blockquote>
<p>I personally just don&#8217;t have time for people that feel they need to use the full extent of their vocabulary in every-day speak.  I&#8217;ve previously worked places where folks were like this a lot, and it was annoying a lot.  It&#8217;s not that I can&#8217;t follow the conversation, but &#8230; get to the frickin point.</p>
<blockquote><p>5: Try to be smarter than the geeks</p></blockquote>
<p>AMEN!  Probably one of my favorite points on the list.  Some of the best management advice I ever heard was, &#8220;Surround yourself with people that are smarter then you.  Then listen to them.&#8221;</p>
<blockquote><p>6: Act inconsistent</p></blockquote>
<p>Well &#8230; I don&#8217;t disagree with it, but this isn&#8217;t particular to managing geeks.  Managers of all types do this.  Yes its bad, but the day I find an employer that doesn&#8217;t do it &#8230; I&#8217;ll kiss their feet.  I don&#8217;t think I&#8217;ll be kissing feet anytime in my life, heh.</p>
<blockquote><p>7: Ignore the geeks</p></blockquote>
<p>Yeah, this happens.  I don&#8217;t really get affected by it to be honest.  I will admit that it is a large factor in me viewing jobs as just a paycheck and nothing more though.</p>
<blockquote><p>8: Make decisions without consulting them</p></blockquote>
<p>Yup.  I agree.  This nearly goes hand-in-hand with point #5 if you ask me.</p>
<blockquote><p>9: DonÇƒÙt give them tools</p></blockquote>
<p>It&#8217;s nice so long as the company can afford it.</p>
<blockquote><p>10: Forget that geeks are creative workers</p></blockquote>
<p>This is probably my favorite on the list.  I look at programming as engineering.  My Dad was/is an Industrial Engineer.  When you need to build something that&#8217;s never been done before, who do you call?  Someone like him.  It&#8217;s the same thing with us in web programming.  Sure, we may not be re-inventing the wheel every day, but our application of the tools we have is rarely the same any two times, and sometimes we&#8217;re completely figuring it out on our own.  It is a creative process. People forget this FAR too often.</p>
]]></content:encoded>
			<wfw:commentRss>http://mattwalters.net/2006/05/27/management-and-geeks/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
