<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress.com" -->
<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/"
	>

<channel>
	<title>coworker-failures &amp;laquo; WordPress.com Tag Feed</title>
	<link>http://en.wordpress.com/tag/coworker-failures/</link>
	<description>Feed of posts on WordPress.com tagged "coworker-failures"</description>
	<pubDate>Fri, 04 Dec 2009 07:54:39 +0000</pubDate>

	<generator>http://en.wordpress.com/tags/</generator>
	<language>en</language>

<item>
<title><![CDATA[Coworkers Considered Harmful]]></title>
<link>http://engtech.wordpress.com/2007/10/15/coworkers-considered-harmful/</link>
<pubDate>Mon, 15 Oct 2007 14:15:07 +0000</pubDate>
<dc:creator>engtech</dc:creator>
<guid>http://engtech.wordpress.com/2007/10/15/coworkers-considered-harmful/</guid>
<description><![CDATA[I hit a realization this weekend that I&#8217;ve hit many times before. There&#8217;s an inordinate ]]></description>
<content:encoded><![CDATA[<div class='snap_preview'><p class="idt-header" style="text-align:center;"><img src="http://engtech.files.wordpress.com/2007/10/workhacks.jpg" alt="Workhacks" /></p>
<p>I hit a realization this weekend that I&#8217;ve hit many times before. There&#8217;s an inordinate number of times when I&#8217;m in the office late not because of my own time management failures but because of the people I work with.</p>
<p>Common coworker induced workplace failures:</p>
<ul>
<li>Checking      in code that doesn&#8217;t work at all</li>
<li>Checking      in code that introduces subtle bugs somewhere else in existing code</li>
<li>Trivial      interruptions when I&#8217;m in a state of flow</li>
<li>Playing      vacation snafu where they schedule a trip immediately after a deliverable</li>
<li>Playing      priority snafu when a manager or team leader side swipes you with fixing      someone else&#8217;s problems that really aren&#8217;t that urgent compared to what      you&#8217;re already working on</li>
<li>Telling      me something I&#8217;m responsible for is broken, when it&#8217;s really because of an      error with the way they&#8217;re using it</li>
<li>Letting      someone convince me of their interpretation of a spec because they are      more experienced and more confident in their opinion</li>
<li>Following their implementation recipe (that doesn&#8217;t work &#8212; particularly from managers who aren&#8217;t in the trenches anymore)</li>
<li>Assuming their code does what the comments describes</li>
<li>Assuming that because a manager asked me for it directly it falls into the 20% of what&#8217;s important, not in the 80% of what can be ignored</li>
</ul>
<p>One of the best lessons you can learn in life is that you can&#8217;t change anyone else, you can only change yourself. The minute you put the blame on someone else you&#8217;ve switch things from being a problem you can control to a problem outside of your control. Up until this point I&#8217;ve put the blame at their feet, but it&#8217;s really my fault because of how I interact with them. It all comes down to a case of trust, and with coworkers trust should be earned, not given (at least when it comes to their assumptions). Here are some things I can do differently to avoid those situations.</p>
<ul>
<li>Always      keep my manager informed of my current priorities and to-do list</li>
<li>Put on      the headphones when I&#8217;m in flow and turn off phone/email</li>
<li>Never,      ever check out coworker code when I&#8217;m in the middle of debugging my own      code</li>
<li>Always      check out a stable version of other coworker code that&#8217;s been show to be      sane so I don&#8217;t spend my time fixing their problems</li>
<li>Read code, use comments as annotations</li>
<li>Always      create interface assertions when integrating with other people&#8217;s code to      easily flag when they&#8217;re not behaving the way they&#8217;re supposed to be</li>
<li>Regressable      unit tests for my own code so that I&#8217;m confident that the problem isn&#8217;t on      my end, and I&#8217;m confident I can introduce changes in my own code without have      side effects</li>
<li>Don&#8217;t believe      a bug exists without seeing it reproduced and seeing the error message</li>
<li>Don&#8217;t      believe my interpretation of spec is wrong without digging into it for      myself</li>
<li>Always be mindful, never follow instructions without thinking it through for myself</li>
</ul>
<p>How have your coworkers unintentionally made your life hell lately?</p>
<p><iframe src='http://digg.com/api/diggthis.php?u=http%3A%2F%2Fdigg.com%2Fpeople%2FCoworkers_Considered_Harmful' height='82' width='55' frameborder='0' scrolling='no' style='float: right; margin-left: 10px; margin-bottom: 5px; padding: 4px 0 2px 4px; background: #fff;'></iframe> (To make it clear &#8212; put your trust and faith into your coworkers, because your relationships with them will get you farther in life than putting your trust into your company ever will. But there&#8217;s a difference between trusting them and blindly trusting their assumptions.)</p>
</div>]]></content:encoded>
</item>

</channel>
</rss>
