<?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: Brian Sabean is Amazing&#8230;</title>
	<atom:link href="http://www.baycityball.com/2008/08/06/brian-sabean-is-amazing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.baycityball.com/2008/08/06/brian-sabean-is-amazing/</link>
	<description>Giants Baseball With a Side of STATS</description>
	<lastBuildDate>Tue, 16 Mar 2010 12:55:18 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MrLomez</title>
		<link>http://www.baycityball.com/2008/08/06/brian-sabean-is-amazing/comment-page-1/#comment-3618</link>
		<dc:creator>MrLomez</dc:creator>
		<pubDate>Fri, 08 Aug 2008 04:40:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.baycityball.com/?p=639#comment-3618</guid>
		<description>To be an apologist for a second:

The way I understand it, right after the TD, it&#039;s not uncommon for teams to basically put everyone on the roster on revocable waivers, from the stars to the bench scrubs (every player can go on R-waivers once a season).  It&#039;s a strategy to mask a team&#039;s intentions in regards to certain fringe players (e.g. Romo) and not necessarily to throw bait out for trade partners.  It&#039;s a pretty weak smokescreen but the idea is that since the whole roster is on RW&#039;s, opposing teams won&#039;t know who to put claims on and who to ignore since they don&#039;t know who you&#039;re serious about unwaiving, releasing, outrighting, etc. (and they can&#039;t just put claims on everyone because then they&#039;re responsible, or potentially responsible, if you then don&#039;t revoke a given player off of waivers).  Deep breath.  Does this make sense?  

Anyway, in the case of Romo, what I imagine happened was he was procedurely placed on R-waivers along with everyone else (or at least a few Giants fringe players), and then the Giants optioned him without considering his status.  The fact that he was on R-waivers to begin with however could very well have been incidental to their decision to option him.

This brainfart is perhaps symbolic of this regime&#039;s inattention to detail, and is pretty shameful.  But practically, it&#039;s not at all that much of a big deal.</description>
		<content:encoded><![CDATA[<p>To be an apologist for a second:</p>
<p>The way I understand it, right after the TD, it&#8217;s not uncommon for teams to basically put everyone on the roster on revocable waivers, from the stars to the bench scrubs (every player can go on R-waivers once a season).  It&#8217;s a strategy to mask a team&#8217;s intentions in regards to certain fringe players (e.g. Romo) and not necessarily to throw bait out for trade partners.  It&#8217;s a pretty weak smokescreen but the idea is that since the whole roster is on RW&#8217;s, opposing teams won&#8217;t know who to put claims on and who to ignore since they don&#8217;t know who you&#8217;re serious about unwaiving, releasing, outrighting, etc. (and they can&#8217;t just put claims on everyone because then they&#8217;re responsible, or potentially responsible, if you then don&#8217;t revoke a given player off of waivers).  Deep breath.  Does this make sense?  </p>
<p>Anyway, in the case of Romo, what I imagine happened was he was procedurely placed on R-waivers along with everyone else (or at least a few Giants fringe players), and then the Giants optioned him without considering his status.  The fact that he was on R-waivers to begin with however could very well have been incidental to their decision to option him.</p>
<p>This brainfart is perhaps symbolic of this regime&#8217;s inattention to detail, and is pretty shameful.  But practically, it&#8217;s not at all that much of a big deal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cat</title>
		<link>http://www.baycityball.com/2008/08/06/brian-sabean-is-amazing/comment-page-1/#comment-3614</link>
		<dc:creator>Cat</dc:creator>
		<pubDate>Wed, 06 Aug 2008 23:54:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.baycityball.com/?p=639#comment-3614</guid>
		<description>And I thought the minor league merry-go-round was bad...</description>
		<content:encoded><![CDATA[<p>And I thought the minor league merry-go-round was bad&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: delorean</title>
		<link>http://www.baycityball.com/2008/08/06/brian-sabean-is-amazing/comment-page-1/#comment-3613</link>
		<dc:creator>delorean</dc:creator>
		<pubDate>Wed, 06 Aug 2008 23:06:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.baycityball.com/?p=639#comment-3613</guid>
		<description>@ OGC:

The buck stops with Sabean. He&#039;s the boss. If something completely f&#039;ing retarded happens on his watch, it&#039;s ultimately his responsibility. Period. 

If it turns out that one of his minions was responsible for this cock-up, then that person needs to be fired immediately, if not sooner. Require some god-damn accountability in your organization.</description>
		<content:encoded><![CDATA[<p>@ OGC:</p>
<p>The buck stops with Sabean. He&#8217;s the boss. If something completely f&#8217;ing retarded happens on his watch, it&#8217;s ultimately his responsibility. Period. </p>
<p>If it turns out that one of his minions was responsible for this cock-up, then that person needs to be fired immediately, if not sooner. Require some god-damn accountability in your organization.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.baycityball.com/2008/08/06/brian-sabean-is-amazing/comment-page-1/#comment-3612</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 06 Aug 2008 20:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.baycityball.com/?p=639#comment-3612</guid>
		<description>But shouldn&#039;t they at least run stuff by him first?

Example: &quot;Hey Boss, I was thinking I might trade Tim Lincecum for Fernando Tatis, whatddya think?&quot;</description>
		<content:encoded><![CDATA[<p>But shouldn&#8217;t they at least run stuff by him first?</p>
<p>Example: &#8220;Hey Boss, I was thinking I might trade Tim Lincecum for Fernando Tatis, whatddya think?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: obsessivegiantscompulsive</title>
		<link>http://www.baycityball.com/2008/08/06/brian-sabean-is-amazing/comment-page-1/#comment-3611</link>
		<dc:creator>obsessivegiantscompulsive</dc:creator>
		<pubDate>Wed, 06 Aug 2008 20:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.baycityball.com/?p=639#comment-3611</guid>
		<description>No, but his assistants are.  Sabean should not be expected to know every nuance of a roster move.  That&#039;s why they had Ned Colletti handling some of that stuff, that&#039;s why Tony Siegel (or a name something like that) was hired, to know the ins and outs of the jungle and jumble of what the procedural rules are.</description>
		<content:encoded><![CDATA[<p>No, but his assistants are.  Sabean should not be expected to know every nuance of a roster move.  That&#8217;s why they had Ned Colletti handling some of that stuff, that&#8217;s why Tony Siegel (or a name something like that) was hired, to know the ins and outs of the jungle and jumble of what the procedural rules are.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.663 seconds -->
