<?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: Sprecher Tasting Notes!</title>
	<atom:link href="http://haveabeer.couchand.com/2009/07/21/sprecher-tasting-notes/feed/" rel="self" type="application/rss+xml" />
	<link>http://haveabeer.couchand.com/2009/07/21/sprecher-tasting-notes/</link>
	<description>For all who appreciate the fermented majesty.</description>
	<lastBuildDate>Wed, 14 Jul 2010 20:55:15 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: couchand</title>
		<link>http://haveabeer.couchand.com/2009/07/21/sprecher-tasting-notes/comment-page-1/#comment-141</link>
		<dc:creator>couchand</dc:creator>
		<pubDate>Tue, 21 Jul 2009 15:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://haveabeer.couchand.com/?p=818#comment-141</guid>
		<description>There are a number of reasons I have things the way they are.

I put the figures at the end of the article because I want to deemphasize the numerical ratings.  The rationale for this is best explained by John David Stone in his article &quot;&lt;a href=&quot;http://www.cs.grinnell.edu/~stone/misc/scales.html&quot; rel=&quot;nofollow&quot;&gt;Scales&lt;/a&gt;&quot;.  The gist of it is that aggregating ratings (such as on a site like RateBeer) commits a statistical fallacy when not everyone&#039;s scales are the same and not everyone weighs each criterion equally.  I would add that even a given person&#039;s scales change over time.  Thus I want to discourage such oversimplification.

This is why I introduced the thumbs up/thumbs down system.  I feel this has significantly more use in giving a person an overall feel for the quality of the beer without attempting to represent it numerically.  However, this is still quite inferior to the actual &lt;em&gt;description&lt;/em&gt; of the beer.  I suppose I hope that after reading my descriptions you would already have an idea of how I would place it on the thumb scale, and since those are color-coded, I figured you would be able to quickly find the relevant ratings.

If you look around at other beer blogs you will note that it is very rare to include any sort of rating.  I believe this is because there is a widespread belief in the primacy of a textual description over a numerical one.  However, to follow the example of Michael Jackson (the Beer Hunter) we try to find something good to say about every beer, and I agree this sometimes does not give a good picture of which beers are decent and which are great.  That is why I have committed to posting ratings as well.

The reason I put them in rating order at the end is purely aesthetic.  I decided I don&#039;t like the jumbled up way it looks when the thumbs are out of order.

So for now I won&#039;t be changing it.  Fortunately I rarely write about more than two beers in a single post so you shouldn&#039;t be inconvenienced too frequently.</description>
		<content:encoded><![CDATA[<p>There are a number of reasons I have things the way they are.</p>
<p>I put the figures at the end of the article because I want to deemphasize the numerical ratings.  The rationale for this is best explained by John David Stone in his article &#8220;<a href="http://www.cs.grinnell.edu/~stone/misc/scales.html" rel="nofollow">Scales</a>&#8220;.  The gist of it is that aggregating ratings (such as on a site like RateBeer) commits a statistical fallacy when not everyone&#8217;s scales are the same and not everyone weighs each criterion equally.  I would add that even a given person&#8217;s scales change over time.  Thus I want to discourage such oversimplification.</p>
<p>This is why I introduced the thumbs up/thumbs down system.  I feel this has significantly more use in giving a person an overall feel for the quality of the beer without attempting to represent it numerically.  However, this is still quite inferior to the actual <em>description</em> of the beer.  I suppose I hope that after reading my descriptions you would already have an idea of how I would place it on the thumb scale, and since those are color-coded, I figured you would be able to quickly find the relevant ratings.</p>
<p>If you look around at other beer blogs you will note that it is very rare to include any sort of rating.  I believe this is because there is a widespread belief in the primacy of a textual description over a numerical one.  However, to follow the example of Michael Jackson (the Beer Hunter) we try to find something good to say about every beer, and I agree this sometimes does not give a good picture of which beers are decent and which are great.  That is why I have committed to posting ratings as well.</p>
<p>The reason I put them in rating order at the end is purely aesthetic.  I decided I don&#8217;t like the jumbled up way it looks when the thumbs are out of order.</p>
<p>So for now I won&#8217;t be changing it.  Fortunately I rarely write about more than two beers in a single post so you shouldn&#8217;t be inconvenienced too frequently.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mr. Izzle</title>
		<link>http://haveabeer.couchand.com/2009/07/21/sprecher-tasting-notes/comment-page-1/#comment-140</link>
		<dc:creator>Mr. Izzle</dc:creator>
		<pubDate>Tue, 21 Jul 2009 13:15:43 +0000</pubDate>
		<guid isPermaLink="false">http://haveabeer.couchand.com/?p=818#comment-140</guid>
		<description>I dislike how ratings are ordered. I wish they were right after the notes in the body of the post, but even if they were in chronological order at the end, it would eliminate much hunting &amp; scrolling.</description>
		<content:encoded><![CDATA[<p>I dislike how ratings are ordered. I wish they were right after the notes in the body of the post, but even if they were in chronological order at the end, it would eliminate much hunting &amp; scrolling.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
