<?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: Against the all nighter</title>
	<atom:link href="http://rc3.org/2010/01/12/against-the-all-nighter/feed/" rel="self" type="application/rss+xml" />
	<link>http://rc3.org/2010/01/12/against-the-all-nighter/</link>
	<description>Rafe Colburn on software development (and other topics)</description>
	<lastBuildDate>Wed, 23 May 2012 22:44:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Nathan L. Walls</title>
		<link>http://rc3.org/2010/01/12/against-the-all-nighter/comment-page-1/#comment-7729</link>
		<dc:creator>Nathan L. Walls</dc:creator>
		<pubDate>Thu, 14 Jan 2010 00:59:18 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10606#comment-7729</guid>
		<description>&lt;blockquote&gt;
  &lt;p&gt;And when they’re requested or demanded, something is going really poorly&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Yes.&lt;/p&gt;

&lt;p&gt;Good planning and requirements don&#039;t require (constant) heroics. Looking back on the times in my career when all-nighters, or their equally abhorrent sibling &quot;working late&quot; were required, they were overwhelming products of the process. In some ways, I could have made them better, but inherently, the projects themselves had structural issues.&lt;/p&gt;

&lt;p&gt;In a management role, I understand there &lt;em&gt;are&lt;/em&gt; cases of poor time-management. But looking at my team, if I&#039;m seeing someone pull an all-nighter, my first question is, &quot;What part of my job did I screw up?&quot;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<blockquote>
  <p>And when they’re requested or demanded, something is going really poorly</p>
</blockquote>

<p>Yes.</p>

<p>Good planning and requirements don&#8217;t require (constant) heroics. Looking back on the times in my career when all-nighters, or their equally abhorrent sibling &#8220;working late&#8221; were required, they were overwhelming products of the process. In some ways, I could have made them better, but inherently, the projects themselves had structural issues.</p>

<p>In a management role, I understand there <em>are</em> cases of poor time-management. But looking at my team, if I&#8217;m seeing someone pull an all-nighter, my first question is, &#8220;What part of my job did I screw up?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stan Taylor</title>
		<link>http://rc3.org/2010/01/12/against-the-all-nighter/comment-page-1/#comment-7724</link>
		<dc:creator>Stan Taylor</dc:creator>
		<pubDate>Tue, 12 Jan 2010 22:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10606#comment-7724</guid>
		<description>&lt;p&gt;As a software QA engineer, I agree completely.&lt;/p&gt;

&lt;p&gt;A QA engineer interview question you sometimes hear is, &quot;Tell me about a time when you had to put your foot down for quality.&quot;&lt;/p&gt;

&lt;p&gt;My response is: if things get to the point where I have to &#039;take a stand for quality&#039;, then the process is seriously broken, and furthermore, I have not done my job of assessing risk throughout the process. That seems similar to me to your &#039;all-nighter.&#039;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>As a software QA engineer, I agree completely.</p>

<p>A QA engineer interview question you sometimes hear is, &#8220;Tell me about a time when you had to put your foot down for quality.&#8221;</p>

<p>My response is: if things get to the point where I have to &#8216;take a stand for quality&#8217;, then the process is seriously broken, and furthermore, I have not done my job of assessing risk throughout the process. That seems similar to me to your &#8216;all-nighter.&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jessamyn</title>
		<link>http://rc3.org/2010/01/12/against-the-all-nighter/comment-page-1/#comment-7720</link>
		<dc:creator>jessamyn</dc:creator>
		<pubDate>Tue, 12 Jan 2010 17:11:32 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10606#comment-7720</guid>
		<description>&lt;p&gt;Oh man, I really had a &quot;scales fell from eyes&quot; moment reading this and the linked essay. Thanks for the nudge Rafe.&lt;/p&gt;

&lt;p&gt;http://www.librarian.net/stax/3126/on-heroism/&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Oh man, I really had a &#8220;scales fell from eyes&#8221; moment reading this and the linked essay. Thanks for the nudge Rafe.</p>

<p><a href="http://www.librarian.net/stax/3126/on-heroism/" rel="nofollow">http://www.librarian.net/stax/3126/on-heroism/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stephen o'grady</title>
		<link>http://rc3.org/2010/01/12/against-the-all-nighter/comment-page-1/#comment-7719</link>
		<dc:creator>stephen o'grady</dc:creator>
		<pubDate>Tue, 12 Jan 2010 14:43:09 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10606#comment-7719</guid>
		<description>&lt;p&gt;every time i&#039;ve had to pull an all nighter, i&#039;ve ended up spending more time later undoing the damage. not to mention that everything took me twice as long when it was three in the morning.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>every time i&#8217;ve had to pull an all nighter, i&#8217;ve ended up spending more time later undoing the damage. not to mention that everything took me twice as long when it was three in the morning.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

