<?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>Caltrain Tweets &#187; Fail</title>
	<atom:link href="http://cow.org/c/archives/category/fail/feed" rel="self" type="application/rss+xml" />
	<link>http://cow.org/c</link>
	<description>Community supported Caltrain notices, one tweet at a time</description>
	<lastBuildDate>Tue, 11 May 2010 23:11:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Really, Caltrain?</title>
		<link>http://cow.org/c/archives/92</link>
		<comments>http://cow.org/c/archives/92#comments</comments>
		<pubDate>Wed, 15 Jul 2009 17:18:30 +0000</pubDate>
		<dc:creator>ravi</dc:creator>
				<category><![CDATA[@caltrain]]></category>
		<category><![CDATA[Commentary]]></category>
		<category><![CDATA[Fail]]></category>

		<guid isPermaLink="false">http://cow.org/c/?p=92</guid>
		<description><![CDATA[I have a meeting at 10AM today and so I hopped on SB232 which would place me in Mountain View with time to spare.  This would be true if a train wasn&#8217;t disabled near Belmont.  Now I&#8217;m not a train engineer or know what it takes to route trains around incidents in a safe way, [...]]]></description>
			<content:encoded><![CDATA[<p>I have a meeting at 10AM today and so I hopped on SB232 which would place me in Mountain View with time to spare.  This would be true if a <a href="http://twitter.com/caltrain/status/2651612038" target="_blank">train wasn&#8217;t disabled near Belmont</a>.  Now I&#8217;m not a train engineer or know what it takes to route trains around incidents in a safe way, but it seems absolutely ridiculous h0w poorly Caltrain has been communicating the delays.</p>
<p>What is even more ridiculous is the <a href="http://twitter.com/caltrain/status/2644658416" target="_blank">back</a> to <a href="http://twitter.com/caltrain/status/2651612038" target="_blank">back</a> issues Caltrain has had.  The constant breakdowns of trains conjures an image of maintenance workers whose voices sound like they have gravel in their throats chewing a stub of a unlit cigar covered in grease.  I can imagine them looking at each other as a new repair is pushed into the depot and they dig into what is nothing short of a junk pile of miscellaneous parts and combined with some chewing gum and duct tape mend the poor dilapidated train into a condition where it can leave on its own power only later to gasp its last burst of power.</p>
<p>This can&#8217;t possibly be the case, right?  I say this because Caltrain spent $140 <strong>million</strong> dollars on &#8220;<a href="http://cow.org/r/?5bfe" target="_blank">repair and maintenance buildings, a state-of-the-art control  center to direct  and monitor train traffic, and storage  yards for Caltrain&#8217;s fleet of locomotives and passenger cars.</a>&#8221;</p>
<p>Actually the same page (which now returns a 404) also says &#8220;Caltrain will have on-site fuel storage,  which will reduce fuel expenses&#8221; yet with the last fare increases they cite rising gas prices.  And of a personal annoyance is the announcement of a &#8220;new train washer that  will allow trains to get a thorough cleaning every day.  Currently, crews are only able to give trains a thorough  washing and scrubbing twice a year.&#8221;  This would be great if they utilized this new ability, but just about every train I am on has windows so filthy I can barely see out the window.  I even wrote feedback to Caltrain about it and they couldn&#8217;t bother to send a reply that they even got the feedback let alone what, if anything, they would do to address my issue.</p>
<p>Well, I&#8217;ve gotten to the point of rant fueled by rage and to make matters worse I&#8217;m on a conference call I want nothing to do with.  And SB332 will end up about 45m behind schedule when all things are done.</p>
<p>What is the lesson learned here?  Stop going into the office.</p>
]]></content:encoded>
			<wfw:commentRss>http://cow.org/c/archives/92/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>I am a giant slacker</title>
		<link>http://cow.org/c/archives/83</link>
		<comments>http://cow.org/c/archives/83#comments</comments>
		<pubDate>Thu, 09 Jul 2009 00:39:31 +0000</pubDate>
		<dc:creator>ravi</dc:creator>
				<category><![CDATA[@caltrain]]></category>
		<category><![CDATA[Fail]]></category>
		<category><![CDATA[fatality]]></category>

		<guid isPermaLink="false">http://cow.org/c/?p=83</guid>
		<description><![CDATA[The last month has been a punch to the face for me work wise and I&#8217;ve fallen behind in generating keys for people and for that I am sorry.  I hope to get some things off my plate and spend some time doing so on my commute this week so be patient.
I had a few [...]]]></description>
			<content:encoded><![CDATA[<p>The last month has been a punch to the face for me work wise and I&#8217;ve fallen behind in generating keys for people and for that I am sorry.  I hope to get some things off my plate and spend some time doing so on my commute this week so be patient.</p>
<p>I had a few small outages with my server in the past few months.  Some were self inflicted and others are still unknown.  It was because of this that I realized I need to establish a backup system that will process email updates if the primary goes down.  I&#8217;m not really sure how to do this per se other than some Postfix and MySQL magic.  I have the infrastructure just not the time.</p>
<p>Edit: And no sooner did I post did was there <a href="http://twitter.com/caltrain/status/2542165190" target="_blank">another fatality</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://cow.org/c/archives/83/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>I&#8217;m fired for being strict</title>
		<link>http://cow.org/c/archives/51</link>
		<comments>http://cow.org/c/archives/51#comments</comments>
		<pubDate>Fri, 05 Dec 2008 17:25:02 +0000</pubDate>
		<dc:creator>ravi</dc:creator>
				<category><![CDATA[Fail]]></category>

		<guid isPermaLink="false">http://cow.org/c/?p=51</guid>
		<description><![CDATA[I broke the service last night while adding the improvements for official update prefixing.  It was a case of not declaring the variable that contains the update in the right place when I moved everything around.  I suppose I could fix this from happening in the future by just not using strict!  Heh.
I apologize if [...]]]></description>
			<content:encoded><![CDATA[<p>I broke the service last night while adding the improvements for <a href="http://cow.org/c/archives/43" target="_blank">official update prefixing</a>.  It was a case of not declaring the variable that contains the update in the right place when I moved everything around.  I suppose I could fix this from happening in the future by just not using strict!  Heh.</p>
<p>I apologize if this jammed up aynone.</p>
<p>I&#8217;m fired.</p>
]]></content:encoded>
			<wfw:commentRss>http://cow.org/c/archives/51/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Caltrain vs. * &#8212; Guess who wins?</title>
		<link>http://cow.org/c/archives/35</link>
		<comments>http://cow.org/c/archives/35#comments</comments>
		<pubDate>Thu, 30 Oct 2008 18:21:36 +0000</pubDate>
		<dc:creator>ravi</dc:creator>
				<category><![CDATA[@caltrain]]></category>
		<category><![CDATA[Commentary]]></category>
		<category><![CDATA[Fail]]></category>
		<category><![CDATA[alert]]></category>

		<guid isPermaLink="false">http://cow.org/c/?p=35</guid>
		<description><![CDATA[Caltrain wins.
KCRA reported at 5:59PDT a incident with a truck and 12m later the @caltrain feed warmed up to a steady stream of updates about track status, train routing, and departures.  While at first I regretted enabling SMS updates for @caltrain because of it waking me up early and keeping me up, I was able [...]]]></description>
			<content:encoded><![CDATA[<p>Caltrain wins.</p>
<p><a href="http://www.kcra.com/" target="_blank">KCRA</a> <a href="http://www.kcra.com/news/17846553/detail.html?rss=sac&amp;psp=news#" target="_blank">reported</a> at 5:59PDT a <a href="http://cow.org/r/?4661" target="_blank">incident with a truck</a> and 12m later the @caltrain feed warmed up to a steady stream of updates about track status, train routing, and departures.  While at first I regretted enabling SMS updates for @caltrain because of it waking me up early and keeping me up, I was able to make alternative plans and ended up carpooling with a friend.</p>
<p>I thought it was amusing to read on a list I am on at 7:52PDT</p>
<blockquote><p>At 4th/King and there are a hundred or so people waiting for multiple<br />
trains. No info on what&#8217;s up.</p></blockquote>
<p>Only to be followed up 8 minutes later with</p>
<blockquote><p>The CalTrain Twitter feed says there&#8217;s a train v. truck in San Mateo,<br />
initially at 9th, finally stopped at 5th.  <a href="http://twitter.com/caltrain" target="_blank">http://twitter.com/caltrain</a></p></blockquote>
<p>I don&#8217;t know about you but does anyone else think it is strange that at a Caltrain terminal this person didn&#8217;t know what was going on?  It would be one thing if it were a unstaffed station, but it is unfortunate it was not clear to what was going on at 4th/King.</p>
<p>I would like to thank everyone again who updaes to make the feed useful to many.</p>
]]></content:encoded>
			<wfw:commentRss>http://cow.org/c/archives/35/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rough day for Caltrain</title>
		<link>http://cow.org/c/archives/10</link>
		<comments>http://cow.org/c/archives/10#comments</comments>
		<pubDate>Wed, 16 Jul 2008 17:26:17 +0000</pubDate>
		<dc:creator>ravi</dc:creator>
				<category><![CDATA[Fail]]></category>
		<category><![CDATA[324]]></category>
		<category><![CDATA[engine]]></category>
		<category><![CDATA[rail]]></category>

		<guid isPermaLink="false">http://cow.org/c/?p=10</guid>
		<description><![CDATA[The last 4 commuting periods where Caltrain has had significant delays I either was carpooling with a co-worker or working from home.  Today is no exception &#8212; I have a cold or something.  Never the less everyone who has been participating in the updating has been doing a fantastic job and today was no exception.  [...]]]></description>
			<content:encoded><![CDATA[<p>The last 4 commuting periods where Caltrain has had significant delays I either was carpooling with a co-worker or working from home.  Today is no exception &#8212; I have a cold or something.  Never the less everyone who has been participating in the updating has been doing a fantastic job and today was no exception.  I woke up to see 12 new SMS on my phone all telling a part of a sad Caltrain story.</p>
<p>For those of you playing at home (or on the train as it were) it appears there was a broken rail near Morgan Hill and SB #324 had engine trouble and had to be combined with SB #230.</p>
]]></content:encoded>
			<wfw:commentRss>http://cow.org/c/archives/10/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Twitter overload</title>
		<link>http://cow.org/c/archives/8</link>
		<comments>http://cow.org/c/archives/8#comments</comments>
		<pubDate>Fri, 27 Jun 2008 23:13:54 +0000</pubDate>
		<dc:creator>ravi</dc:creator>
				<category><![CDATA[Fail]]></category>
		<category><![CDATA[broken]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://cow.org/c/?p=8</guid>
		<description><![CDATA[Twitter was overloaded this morning and three tweets were lost to a 500 read timeout.  They were (GMT -5):
Fri Jun 27 11:39:02 2008:24834: Tweet: &#8216;230 old 1car: 332 new 1 car&#8217;
Fri Jun 27 11:52:06 2008:25590: Tweet: &#8216;NB329 5min late at Millbrae&#8217;
Fri Jun 27 11:56:18 2008:25865: Tweet: &#8216;SB230 old style 1 car; room after 22nd&#8217;
I am [...]]]></description>
			<content:encoded><![CDATA[<p>Twitter was overloaded this morning and three tweets were lost to a 500 read timeout.  They were (GMT -5):</p>
<blockquote><p>Fri Jun 27 11:39:02 2008:24834: Tweet: &#8216;230 old 1car: 332 new 1 car&#8217;</p>
<p>Fri Jun 27 11:52:06 2008:25590: Tweet: &#8216;NB329 5min late at Millbrae&#8217;</p>
<p>Fri Jun 27 11:56:18 2008:25865: Tweet: &#8216;SB230 old style 1 car; room after 22nd&#8217;</p></blockquote>
<p>I am still on the fence on how to handle failed updates.  I suppose I could retry 3 times or so, but anything more may run the risk of having the tweet become unnewsworthy.  Any thoughts?</p>
]]></content:encoded>
			<wfw:commentRss>http://cow.org/c/archives/8/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
