<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Computerjargon.com &#187; on-call</title>
	<atom:link href="http://www.computerjargon.com/tag/on-call/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.computerjargon.com</link>
	<description>The Life of Jason Motylinski</description>
	<lastBuildDate>Wed, 10 Dec 2008 22:38:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>On Call Confusion</title>
		<link>http://www.computerjargon.com/2007/08/08/on-call-confusion/</link>
		<comments>http://www.computerjargon.com/2007/08/08/on-call-confusion/#comments</comments>
		<pubDate>Wed, 08 Aug 2007 20:42:21 +0000</pubDate>
		<dc:creator>Jason Motylinski</dc:creator>
				<category><![CDATA[Personal]]></category>
		<category><![CDATA[cellphones]]></category>
		<category><![CDATA[on-call]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.computerjargon.com/2007/08/08/on-call-confusion/</guid>
		<description><![CDATA[&#8220;I&#8217;m supposed to give you this, &#8221; he said with a thrust of an object.
&#8220;Oh, okay, is there anything I should know about it?&#8221;
&#8220;Yeah, i didn&#8217;t charge it last night so you&#8217;re gonna want to plug it in.&#8221; With those kinds of instructions, I knew I was in for trouble.
I managed to avoid &#8220;on-call&#8221; duty [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;I&#8217;m supposed to give you this, &#8221; he said with a thrust of an object.</p>
<p>&#8220;Oh, okay, is there anything I should know about it?&#8221;</p>
<p>&#8220;Yeah, i didn&#8217;t charge it last night so you&#8217;re gonna want to plug it in.&#8221; With those kinds of instructions, I knew I was in for trouble.</p>
<p>I managed to avoid &#8220;on-call&#8221; duty at work for my first 2 months of my new job. I knew I couldn&#8217;t avoid it much longer. My day had come.</p>
<p>My co-worker had handed me a Blackberry with no instructions on how to use it or how I go about answering support issues. I took the phone with little regard, nervous about what could happen with it in my possession.  I checked to make sure I knew how to turn it on, check the contact list, and check out the Bricks game everyone was raving about. I put it on the charger as suggested and waited.</p>
<p>I took my new found nemesis home with me.  I checked the call logs on the phone to glean any type of information I could about call frequency, duration, and especially time. Nothing looked out of the ordinary. In fact, over the course of the previous shift my co-worker had only one issue during work hours. I could handle that.  I put the phone on my dresser and we went to bed.</p>
<p><em> Buzz, buzz, BEEP BEEP BEEP!</em></p>
<p>11pm, the cell rings. I literally fall out of bed running to answer the thing. &#8220;Oh great, just must luck,&#8221; I think. I grab the phone and run out of the bedroom so I don&#8217;t disturb Courtney. There&#8217;s a message on the phone. &#8220;I didn&#8217;t even hear it ring!&#8221; I mutter. I fall into the kitchen and turn on some lights to help me concentrate.</p>
<p>Scroll, scroll, push button, scroll, push&#8230;&#8221;What the hell?&#8221; From what I can tell the Blackberry had received an email, not a phone call. I read through the email and it&#8217;s a server check telling me that a server fell offline and came back online a minute later (for the uninitiated, that&#8217;s quite common). Whew, no major issue, no action required. I head back to bed.</p>
<p><em>Buzz, buzz, BEEP BEEP BEEP!</em></p>
<p>&#8220;JESUS!&#8221; 5 minutes later the phone starts humming again. I repeat the same process: grab phone, run out to kitchen, check messages. Again, it&#8217;s just more server checks.  &#8220;Godammit&#8230;&#8221; I go back to bed.</p>
<p><em>Buzz, buzz, BEEP BEEP BEEP!</em></p>
<p>&#8220;For F&#8217;s SAKE!&#8221; I shout in my quiet voice. The phone marches across the dresser again at 2am. By this point I have already lost about an hours worth of sleep. I was just getting back into the swing of things when it started ringing. I quickly check. More server checks. I&#8217;m going to throw this thing across the room at any moment.</p>
<p><em>Buzz, buzz, BEEP BEEP BEEP!</em></p>
<p>&#8220;Oh, this is just plain ridiculous, &#8221; I tell Court, who is also awake. &#8220;They&#8217;re just emails! Not even messages!&#8221;</p>
<p>&#8220;Can&#8217;t you turn off the message notifications?&#8221; She asks.</p>
<p>&#8220;NO!&#8221; I say and go back to bed. The real answer to her question is &#8220;Yes, just not at 2:30am when I&#8217;m drowsy and pissed off.&#8221;</p>
<p>I think it buzzed one last time at 4:30am. By that time I had been awake more than asleep that it didn&#8217;t really phase me. I compared my late night experience with the previous week on call. Sure enough it was my shift that received the most over night notifications.</p>
<p>When I got into work I asked my co-worker about the server checks.  He said, &#8220;Well, if it&#8217;s REALLY important, someone will end up calling you anyway.&#8221; That&#8217;s what I thought.</p>
<p>Night 1 down, 6 more to go.</p>
<h2 class="widgettitle">Related Posts</h2><ul class="related_post"><li><a href="http://www.computerjargon.com/2008/04/05/never-gonna-give-you-up-never-gonna-let-you-down/" title="Never Gonna Give You Up, Never Gonna Let You Down">Never Gonna Give You Up, Never Gonna Let You Down</a></li><li><a href="http://www.computerjargon.com/2007/11/21/igot-an-iphone/" title="iGot an iPhone">iGot an iPhone</a></li><li><a href="http://www.computerjargon.com/2007/10/01/no-rest-for-the-weary/" title="No Rest for the Weary">No Rest for the Weary</a></li><li><a href="http://www.computerjargon.com/2007/08/15/smoke-signals/" title="Smoke Signals">Smoke Signals</a></li><li><a href="http://www.computerjargon.com/2007/06/25/after-work-after-bar/" title="After Work After Bar">After Work After Bar</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.computerjargon.com/2007/08/08/on-call-confusion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
