<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html" />
  <link rel="self" type="application/atom+xml" href="http://consumerist.com/atom.xml" />
  <id>tag:consumerist.com,2010:/1/tag:64.14.177.195,2008://1.5120395-</id>
  <updated>2010-01-24T14:07:10Z</updated>
  <title>Comments for Cheat Sheet for Sketchy Food Expiration &apos;Codes&apos;</title>
  <subtitle>Shoppers bite back.</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.32-en</generator>
  <entry>
    <id>tag:64.14.177.195,2008://1.5120395</id>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://consumerist.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=5120395" title="Cheat Sheet for Sketchy Food Expiration 'Codes'" />
    <published>2008-12-30T19:00:00Z</published>
    <updated>2008-12-30T20:05:15Z</updated>
    <title>Cheat Sheet for Sketchy Food Expiration &apos;Codes&apos;</title>
    <summary>--&gt;Brian, you are the man. After seeing yesterday&apos;s post regarding the confusing expiration codes found on some foods, Brian sent The Consumerist a handy cheat sheet explaining the various code format, found inside. A+.</summary>
    <author>
      <name>Alex Jarvis</name>
      
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://consumerist.com/">
      <![CDATA[<p><!--<img src="http://consumerist.com/images/31/2008/12/thumbs_up_02_01.jpg" width="314" height="192">-->Brian, you are the man. After seeing yesterday's post regarding the confusing expiration codes found on some foods, Brian sent The Consumerist a handy cheat sheet explaining the various code format, found inside. A+.</p>]]>
      <![CDATA[<p><img src="http://consumerist.com/images/31/2008/12/codepage1.JPG"    style="display:block;" /></p>
<p><img src="http://consumerist.com/images/31/2008/12/codepage2.JPG"    style="display:block;" /></p>
<p><img src="http://consumerist.com/images/31/2008/12/Codepage3.JPG"    style="display:block;" /></p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:10951790</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c10951790" />
    <title>Comment from Anonymous on 2009-02-24</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>A few people have said it's "easier" to work out how long until expiry by using ordinal dates. And, I agree, it's easier if you happen to have the current ordinal date memorised, as all shoppers are apparently expected to.

<p>But why no go the whole hog, and use actual Julian dates? Or I suppose we could get away with reduced Julian dates and use only 5 digits, which would keep the people insisting on short codes happy, too.</p>

<p>That way, even if the year rolls over between you buying something and its expiration date, it's still just a  matter of simple subtraction. If today is 54886, and a product has an expiry date of 54952, we know there's a good couple of months before it goes off, right? How could anyone object to this cunning plan?</p></p>]]>
    </content>
    <published>2009-02-24T22:09:56Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9801221</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9801221" />
    <title>Comment from Anonymous on 2009-01-04</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Stuff in cans NEVER expires unless the can is bulging in which case its botulism and is deadly. 
I've eaten Progresso soup that was five years old and it was fine. It's a plot to get you to throw out perfectly good food and buy more.</p>]]>
    </content>
    <published>2009-01-04T12:27:06Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9798776</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9798776" />
    <title>Comment from Anonymous on 2009-01-04</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9729536" rel="nofollow">shorty63136</a>:  I think an easy way to answer any question is to begin by opening a web browser, then typing into the "Address Bar" the following "www.google.com" after which you can enter any type of query you have.

<p>Another option is wikipedia.org</p>

<p>Give a man a fish and he'll eat for a day, teach a man to fish an he'll eat for a lifetime.</p></p>]]>
    </content>
    <published>2009-01-04T05:51:47Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9796750</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9796750" />
    <title>Comment from Anonymous on 2009-01-03</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9731944" rel="nofollow">ZekeSulastin</a>: That international standard is <a href="http://en.wikipedia.org/wiki/ISO_8601" rel="nofollow">ISO 8601</a> (YYYY-MM-DD). It even supports ordinal dates (YYYY-DDD) which are incorrectly referred to as Julian dates in this article.</p>]]>
    </content>
    <published>2009-01-04T02:39:50Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9796574</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9796574" />
    <title>Comment from Anonymous on 2009-01-03</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9730179" rel="nofollow">snowburnt</a>: Actually, using dd/mm/yyyy would be more confusing. You would wind up with foods that expire in different months lumped together as in 1/1/2009,1/2/2009,1/3/2009, and 11/2/2009. Compared to 1/1/2009,2/1/2009,2/11/2009, and 3/1/2009. Putting the month first makes more sense especially when sorting by computer, although yyyy/mm/dd would be best.</p>]]>
    </content>
    <published>2009-01-04T02:25:42Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9796113</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9796113" />
    <title>Comment from Anonymous on 2009-01-03</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Beer date codes are somewhat different, at least in Canada. Domestic brands have a code that starts with a letter A through M. A = January, B = February, etc.. The following two number say the day of the month brewed, followed by a third number which is the year. the numbers afterward are just brewing lines and times. 

<p>Various import brands have various ways of doing things as well. Corona Reads as mm-dd-yy, and Heineken is read as the first three numbers in the code being the day of the year (1-365) with the following number being the year.</p>

<p>So alcohol can be pretty obscure, but expired liquor will rarely make you sick.</p></p>]]>
    </content>
    <published>2009-01-04T01:45:14Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9795846</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9795846" />
    <title>Comment from Anonymous on 2009-01-03</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>To all us colorblind folk, you may not see it at first, but the examples are duo-toned ... the 'Explanation' corresponds to the red letters (that are very difficult for me and other i'm sure to see) in the example.  Before someone pointed this out to me, I was scratching my head thinking, "this chart makes it even MORE confusing" :-P</p>]]>
    </content>
    <published>2009-01-04T01:20:43Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9795210</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9795210" />
    <title>Comment from Anonymous on 2009-01-03</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>You need to look at the whole idea of "expiration".  It is not a magical date where the product are buying turns to crap at midnight on the appointed date.  Depending on your views of a company, they put a date that will legally cover them in case something happens, their "suggested expiration", or to maintain quality control.  Looking back ten years ago, Campbell's soup had no expiration codes, and I can pretty much guarantee you that everyone has a few cans that are years old in their cupboards.  You telling me that they are expired?  It never occured to you until someone printed a date on them.
BTW, manufacturer's also use those codes to protect their own profits.  By legitimately, or artifically, putting specific code dates on products, they are guaranteed to have a wholesaler continually buying from them.  The code date ensures that a retailer cannot buy too large a quantity on a product, for fears that it will expire.
If you would like to check, look at a can of Ocean Spray Cranberries.  The expiration date will ALWAYS be the second or third week in November.  Why?  So a retailer cannot buy two year's inventory for Thanksgiving.  It is just one example of many.
You can only trust the code as much as you trust the manufacturer.  You can only trust the product as much as you can trust the retailer to handle it properly.  Don't look for some magical date to make everything all better.</p>]]>
    </content>
    <published>2009-01-04T00:14:54Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9795019</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9795019" />
    <title>Comment from Anonymous on 2009-01-03</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>They should follow the genealogical standard (those people know dates) DD MMM YYYY. Month uses letters. 
eg. 01 JAN 2009

<p>No confusion possible with a format like that. </p></p>]]>
    </content>
    <published>2009-01-03T23:51:49Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9794849</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9794849" />
    <title>Comment from LazyNinja on 2009-01-03</title>
    <author>
        <name>LazyNinja</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9772331" rel="nofollow">aliencam</a>: <br />
That's the current format being used by the company. They haven't used the format on the list in over 5 years. In other words that list is VERY out of date. You'll always find the DD/MM/YY or YY/MM/DD format on Kraft/Nabisco products.</p>]]>
    </content>
    <published>2009-01-03T23:34:28Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9794814</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9794814" />
    <title>Comment from Anonymous on 2009-01-03</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>The company I work for uses the following format for it's use by date:
L## JulianDate Time(24H)
Normally, in my experience, the L## represents the line number that the product was cooked/packaged on.</p>]]>
    </content>
    <published>2009-01-03T23:31:16Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9794388</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9794388" />
    <title>Comment from Anonymous on 2009-01-03</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I believe the term ordinal date is better used in this situation than Julian Date.</p>]]>
    </content>
    <published>2009-01-03T22:39:30Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9794359</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9794359" />
    <title>Comment from SidoniaRattlesnake on 2009-01-03</title>
    <author>
        <name>SidoniaRattlesnake</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>ok so this is obviously an excel spreadsheet.  please post it directly so we can use it instead of screenshots.</p>]]>
    </content>
    <published>2009-01-03T22:35:23Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9794011</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9794011" />
    <title>Comment from Anonymous on 2009-01-03</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I don't understand. Expiration dates are for health and safty purposes so you don't eat a year old peanut and die! So then, WHY THE HELL are these formats so convoluted and hard to understand. I appreciate the info though. </p>]]>
    </content>
    <published>2009-01-03T21:54:56Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9793980</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9793980" />
    <title>Comment from Anonymous on 2009-01-03</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9731366" rel="nofollow">Rob Weddle</a>: I don't exactly disagree with that comment.  In fact, most of the time I completely agree.  However, I live somewhere cold and can be snowed in for days or potentially weeks.  Its pretty hard to get a fresh apple in the middle of nowhere when there are no usable roads.  What should I do?  Buy fresh when I can and then process the food myself so it will last longer like people did 100 years ago?  Still has to be processed to last more than a couple days.  If I'm picky about what I buy I don't see any reason I should need to.  Just because its in a can doesn't mean its bad for you.</p>]]>
    </content>
    <published>2009-01-03T21:51:43Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9793242</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9793242" />
    <title>Comment from RvLeshrac on 2009-01-03</title>
    <author>
        <name>RvLeshrac</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9755333" rel="nofollow">ShwetaNanobutt</a>:</p><br />
<p>Many foods can, yes. Most of them aren't packaged to last forever. The only reason you don't see many stories about illness is because it is typically minor (a tummyache and throwing up isn't newsworthy), and there are signs that food has gone bad (smell, taste, large green masses).</p><br />
<p>That said, a food past the expiration date isn't necessarily going to do anything to you. My stepfather once accidentally ate some months-expired mayo on a sandwich, and aside from a comment about it tasting a little funny (which led to the expiration date check), no harm was done.</p><br />
<p>The rule of thumb is "when in doubt, throw it out." In these tough economic times, however, you can safely (for SOME products, I highly recommend against eating, say, expired meat) amend that to "when in doubt, taste a very small amount and wait several hours to see if there are any ill effects." I'd probably throw out most anything refrigerated after a week-past.</p><br />
<p>Four month old mayo might not hurt you once, but we didn't exactly make another sandwich with it.</p></p>]]>
    </content>
    <published>2009-01-03T19:22:20Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9776108</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9776108" />
    <title>Comment from puka_pai on 2009-01-02</title>
    <author>
        <name>puka_pai</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9749441" rel="nofollow">TaterTom</a>: </p><blockquote>It looks like the trends in date labeling can also be applied to alcohol and tobacco products, as well. Can someone confirm/correct me?</blockquote>
<p>Off the top of my head, I know that Copenhagen has a "made on" date, Skoal has a "fresh until" date and Grizzly has some incomprehensible code. I haven't paid attention to the dates on cigarettes, but I haven't seen any that aren't coded in some way that makes it hard for humans to understand.</p>]]>
    </content>
    <published>2009-01-02T15:09:54Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9772331</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9772331" />
    <title>Comment from aliencam on 2009-01-01</title>
    <author>
        <name>aliencam</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I have some Nabisco products that do not use the code listed above.  Wheat thins with a code in the format: 30JAN07, which I take to mean january 30th 2007 they will have gone bad (wow this box is still unopened in my pantry)  and Ritz with the code 05SEP08,</p>]]>
    </content>
    <published>2009-01-02T00:57:03Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9767221</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9767221" />
    <title>Comment from coren on 2009-01-01</title>
    <author>
        <name>coren</name>
        <uri>n/a</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="n/a">
        <![CDATA[<p>@<a href="#c9749251" rel="nofollow">P_Smith</a>: I picked up on it - I'm suggesting standardized system so ambiguity doesn't exist.</p>]]>
    </content>
    <published>2009-01-01T06:55:28Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9765941</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9765941" />
    <title>Comment from Anonymous on 2008-12-31</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Why is it legal for them to print stuff that is not easily read that could effect your health if you eat something expired?  There is no magic to printing this stuff, why not just print it so we can all read it?</p>]]>
    </content>
    <published>2009-01-01T04:59:47Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9761600</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9761600" />
    <title>Comment from timsgm1418 on 2008-12-31</title>
    <author>
        <name>timsgm1418</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9752352" rel="nofollow">RvLeshrac</a>: only a guess, but they might want "made on" dates in case of recalls, they could narrow down the lots or batches whatever...just a guess, don't know this for sure</p></p>]]>
    </content>
    <published>2009-01-01T01:04:34Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9755333</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9755333" />
    <title>Comment from Anonymous on 2008-12-31</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Can eating old or outdated food actually cause illness?  Sure, the nutritional values would probably be compromised, and I'm not saying that it's acceptable that we don't have a reliable way to know how long this junk has been sitting around.  I'm just curious about documented cases of illness... bulging cans of botulism notwithstanding.</p>]]>
    </content>
    <published>2008-12-31T21:08:59Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9752454</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9752454" />
    <title>Comment from RvLeshrac on 2008-12-31</title>
    <author>
        <name>RvLeshrac</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>I *think* most bread makers have switched to expiration dates... but if not, does anyone have a current list of "twist-tie dating" codes?</p><br />
<p>For those who don't know: 'twist-tie' dating was/is how many sandwich breads are/were dated - different colors for different days of the week. That's why you'd see red twist-ties one day, and blue/white/yellow/black/orange/tan/etc the next. It made things easy on the bread delivery guy, since instead of having to pick up every loaf of bread on the shelf, he could simply look at the tie. If the tie was the same color as the ties on the new delivery, the ones already on the shelf would get thrown out (last week's bread).</p></p>]]>
    </content>
    <published>2008-12-31T17:58:45Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9752416</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9752416" />
    <title>Comment from RvLeshrac on 2008-12-31</title>
    <author>
        <name>RvLeshrac</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9747689" rel="nofollow">coren</a>:</p><br />
<p>You will expire several hundred, if not thousands, of years before a *properly* canned/bottled food product. Now, they won't taste particularly good by that point, but if you can get them down, they'll keep you nourished. (Imagine eating completely tasteless, likely formless, mass. Think 'mashed tofu.')</p><br />
<p>Any canned foods with "Expiration" dates aren't really "canned," they're just "packaged in a can." Lots of vegetables suffer from this malady - ostensibly, that particular packing method is used to keep them from losing more nutrients. "Best By" dates are more common on canned goods, given the eventual loss of flavor and texture.</p><br />
<p>From <a href="http://www.hormelfoods.com/faqs.aspx#can4" rel="nofollow">[www.hormelfoods.com]</a> :</p><br />
<p>"What is the shelf life of a Hormel Foods product in an unopened can?</p><br />
<p>The processing techniques utilized by Hormel Foods makes the canned product safe for use indefinitely if the product seal remains intact, unbroken and securely attached to a can that has been well maintained. It is suggested that all canned products be stored in a cool and dry environment to keep the flavor adequately preserved. For maximum flavor it is recommended that the product be used within three years of the manufacturing date. After that period of time, the product is still safe to use however, the flavor gradually declines."</p><br />
<p>This is why, when you make an emergency shelter or prep an emergency kit, you stock cans of SPAM, pickles, etc.</p></p>]]>
    </content>
    <published>2008-12-31T17:52:04Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9752353</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9752353" />
    <title>Comment from RvLeshrac on 2008-12-31</title>
    <author>
        <name>RvLeshrac</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9733527" rel="nofollow">richcreamerybutter</a>:</p><br />
<p>Since we're talking expiration dates, if you find a product that has an expiry date of pre-current-year, you bin it.</p></p>]]>
    </content>
    <published>2008-12-31T17:36:31Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9752352</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9752352" />
    <title>Comment from RvLeshrac on 2008-12-31</title>
    <author>
        <name>RvLeshrac</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9732691" rel="nofollow">CityGuySailing</a>:</p><br />
<p>As I posted earlier, I swear the calendar said "2008" and not "1408."</p><br />
<p>We have computers to handle this. They'll tell you everything up to and including from where, exactly, a pallet should be pulled in order to remove the oldest product.</p><br />
<p>And why are manufacturers printing "made on" dates instead of "expires on" dates? You don't need to do any math whatsoever when one product expires "2009-07-06" and another expires "2013-03-18." You start from the left, and whichever one has a lower number first wins.</p></p>]]>
    </content>
    <published>2008-12-31T17:35:37Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9752333</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9752333" />
    <title>Comment from RvLeshrac on 2008-12-31</title>
    <author>
        <name>RvLeshrac</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9731366" rel="nofollow">Rob Weddle</a>:</p><br />
<p>So you're suggesting that we milk our own cows, producing our own cheeses and other dairy products, slaughter our own meat, etc?</p><br />
<p>I looked at the calendar today, and I could swear it said "December 31, 2008," not "December 31, 1461."</p><br />
<p>*All* food is "processed," not all food is processed in the same way. Your apple, for instance, was likely coated with a thin layer of wax to ensure a longer shelf life.</p></p>]]>
    </content>
    <published>2008-12-31T17:30:16Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9751220</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9751220" />
    <title>Comment from mmmsoap on 2008-12-31</title>
    <author>
        <name>mmmsoap</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9729652" rel="nofollow">VereKlimchuck</a>: You and I seem to have different definitions of the word "slightly."</p>]]>
    </content>
    <published>2008-12-31T12:24:54Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9749441</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9749441" />
    <title>Comment from TaterTom on 2008-12-31</title>
    <author>
        <name>TaterTom</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>This is one AWESOME post. No longer will I have to consult my mother [former customer service for multiple food brands] about whether or not I'll get sick from eating stuff.</p>
<p>It looks like the trends in date labeling can also be applied to alcohol and tobacco products, as well. Can someone confirm/correct me?</p>]]>
    </content>
    <published>2008-12-31T09:13:32Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9749251</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9749251" />
    <title>Comment from P_Smith on 2008-12-31</title>
    <author>
        <name>P_Smith</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="#c9747641" rel="nofollow">coren</a>: <i>Or YYMM - I seriously doubt we've got food to last 100 years.</i></p><br />
<p>As I said the first time but you didn't pick up on, four characters could cause ambiguity in the current two decades.  Does 0809 mean September 2008 or August 2009?  Six characters would avoid that in the years 2000-2016, the rough shelf life of canned or dried goods.</p></p>]]>
    </content>
    <published>2008-12-31T08:59:41Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9747689</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9747689" />
    <title>Comment from coren on 2008-12-31</title>
    <author>
        <name>coren</name>
        <uri>n/a</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="n/a">
        <![CDATA[<p>I'm assuming Y when it is a single digit represents the 1 column of years (like next year would be 9)?  Then again I'm also assuming we don't have processed food with a shelf life of 10 years yet...</p>]]>
    </content>
    <published>2008-12-31T07:06:04Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9747668</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9747668" />
    <title>Comment from coren on 2008-12-31</title>
    <author>
        <name>coren</name>
        <uri>n/a</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="n/a">
        <![CDATA[<p>@<a href="#c9734038" rel="nofollow">Orv</a>: I see 2 and 3 - but 1?  That's an argument for the other side - you'd have to know how many days hath September to calculate a Julian date.  A simple date of the year would make that easier</p>]]>
    </content>
    <published>2008-12-31T07:04:04Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9747641</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9747641" />
    <title>Comment from coren on 2008-12-31</title>
    <author>
        <name>coren</name>
        <uri>n/a</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="n/a">
        <![CDATA[<p>@<a href="#c9740782" rel="nofollow">P_Smith</a>: Or YYMM - I seriously doubt we've got food to last 100 years.</p>]]>
    </content>
    <published>2008-12-31T07:01:43Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9747628</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9747628" />
    <title>Comment from coren on 2008-12-31</title>
    <author>
        <name>coren</name>
        <uri>n/a</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="n/a">
        <![CDATA[<p>@<a href="#c9740587" rel="nofollow">P_Smith</a>: That would be a point for stores not to do it - but they have no control over it, it's manufacturers, whoa re out of the process by then.</p>]]>
    </content>
    <published>2008-12-31T07:01:08Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9747618</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9747618" />
    <title>Comment from coren on 2008-12-31</title>
    <author>
        <name>coren</name>
        <uri>n/a</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="n/a">
        <![CDATA[<p>@<a href="#c9734846" rel="nofollow">thrlsekr</a>: I don't know that they don't want the store to know either - I mean, one could argue that if the store did know, they would dump that inventory and buy more sooner...of course the other side of that argument is pretty compelling too</p>]]>
    </content>
    <published>2008-12-31T07:00:23Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9743821</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9743821" />
    <title>Comment from MooseOfReason on 2008-12-30</title>
    <author>
        <name>MooseOfReason</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9733676" rel="nofollow">richcreamerybutter</a>: I'm sure it's very possible.  It could scan the expiration code, read it, and turn it into a date format you're comfortable reading.</p>
<p>The T-Mobile G1 already has a barcode scanner.<br />
<a></a></p>]]>
    </content>
    <published>2008-12-31T03:47:05Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9743765</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9743765" />
    <title>Comment from MooseOfReason on 2008-12-30</title>
    <author>
        <name>MooseOfReason</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9729887" rel="nofollow">socialSTD</a>: @<a href="#c9729887" rel="nofollow">socialSTD</a>: @<a href="#c9731366" rel="nofollow">Rob Weddle</a>: But wait, you mean if I wanted to know what the weather was, I could look outside!?</p>
<p>Still, you wouldn't know how the produce looked on the inside until you bought it, took it home, and cut it open.  My grandma always has problems with avocados.  Half the time, she cuts them open and they're nasty inside.</p>
<p>Also, you can't - or you're not supposed to - open a box of cookies or crackers, or any other product, and check out how they look.</p>]]>
    </content>
    <published>2008-12-31T03:44:44Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9742216</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9742216" />
    <title>Comment from AlxFherMana on 2008-12-30</title>
    <author>
        <name>AlxFherMana</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9730639" rel="nofollow">OprahBabb</a>: Same.</p>
<p>Usually it's not too difficult to read the labels, but lately I have spent a lot of time turning products every which way to see what combo of numbers is the expiration date...It would also help if they PRINTED the date instead of embossing it (or whatever that's called) on the white part of a cardboard package so you have to find the right angle in order to read it...</p>]]>
    </content>
    <published>2008-12-31T02:49:18Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9742103</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9742103" />
    <title>Comment from AlxFherMana on 2008-12-30</title>
    <author>
        <name>AlxFherMana</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9731751" rel="nofollow">Ein2015</a>: Hehe.</p>]]>
    </content>
    <published>2008-12-31T02:45:40Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9740782</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9740782" />
    <title>Comment from P_Smith on 2008-12-30</title>
    <author>
        <name>P_Smith</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="#c9730127" rel="nofollow">ChristopherDavis</a>: <i>This is true, but there's an ISO standard format for dates for a reason. (YYYY-MM-DD, which has advantages including being able to be sorted lexically as well as being unambiguous.) Unfortunately, 10 characters is a lot of space to take up on a food label just for a date.</i></p><br />
<p>So what's wrong with printing six characters (YYYYMM)?  Four characters might cause ambiguity for the current two decades we're in, but aside from that, four characters is within 30 days of accuracy, good enough for most packaged foods.</p></p>]]>
    </content>
    <published>2008-12-31T02:07:20Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9740671</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9740671" />
    <title>Comment from P_Smith on 2008-12-30</title>
    <author>
        <name>P_Smith</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="#c9730179" rel="nofollow">snowburnt</a>: <i>don't they do DD/MM/YYYY in Europe? Makes a lot more sense than doing MM/DD/YYYY...</i></p><br />
<p>Going YY/DD/MM or MM/DD/YY makes as much sense as a watch that lists time by hours/seconds/minutes.</p></p>]]>
    </content>
    <published>2008-12-31T02:03:59Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9740587</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9740587" />
    <title>Comment from P_Smith on 2008-12-30</title>
    <author>
        <name>P_Smith</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="#c9730119" rel="nofollow">JohnDeere</a>: <i>they would lose sales. if you cant read it you dont know its went bad and you buy it anyway.</i></p><br />
<p>Bingo.  How many people are going to make the effort to take a spoilt $2 product back to the store the next time they shop?  And how many of them are going to do it within the usual refund period, within 14 days of purchase?  They're betting on people just throwing it out.</p><br />
<p><i>"You bought this three weeks ago!  You should have brought it sooner, now we can't refund the money.  It doesn't matter that you don't shop here that often."</i>  I've heard that load of crap once or twice, even on products that weren't past their due date but were "off" (e.g. eggs).</p></p>]]>
    </content>
    <published>2008-12-31T02:00:53Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9740381</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9740381" />
    <title>Comment from thrashanddestroy on 2008-12-30</title>
    <author>
        <name>thrashanddestroy</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9731751" rel="nofollow">Ein2015</a>: Unintentional morning pun, but pun nonetheless!</p>]]>
    </content>
    <published>2008-12-31T01:53:10Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9734846</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9734846" />
    <title>Comment from thrlsekr on 2008-12-30</title>
    <author>
        <name>thrlsekr</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9730119" rel="nofollow">JohnDeere</a>: How would they lose sales? Once the product is on the shelf the manufacturer sold the product and it is up to the retailer to sell the product. The manufacturer does not want the retailer to easily have their staff determine what is out of date and what is not! The manufacturer does not take the expired products back so it is the retailer who will lose if the product is not sold.</p>]]>
    </content>
    <published>2008-12-30T23:07:10Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9734082</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9734082" />
    <title>Comment from Orv on 2008-12-30</title>
    <author>
        <name>Orv</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9732245" rel="nofollow">Xkeeper</a>: Yes, but that only works for English-speaking countries.  Every language has its own words for the months of the year.</p>]]>
    </content>
    <published>2008-12-30T22:40:50Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9734038</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9734038" />
    <title>Comment from Orv on 2008-12-30</title>
    <author>
        <name>Orv</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9732046" rel="nofollow">lannister80</a>: There are three reasons that I can think of to use Julian dates.</p>
<p>- It makes the math easier for humans, when they're trying to figure out how old something is.  Just find today's Julian date and subtract.  None of this "thirty days hath September" stuff.</p>
<p>- It's easier for equipment to generate.  Just increment once per day until you hit 365 or 366.  Not such a big deal now, but once upon a time these date stamps were generated by mechanical counters, and adding logic to handle months of varying lengths would have greatly complicated things.</p>
<p>- It takes up less space on the label.</p>]]>
    </content>
    <published>2008-12-30T22:39:46Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9733676</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9733676" />
    <title>Comment from richcreamerybutter on 2008-12-30</title>
    <author>
        <name>richcreamerybutter</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Also, someone should convert this into an Iphone app!</p>]]>
    </content>
    <published>2008-12-30T22:29:04Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9733527</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9733527" />
    <title>Comment from richcreamerybutter on 2008-12-30</title>
    <author>
        <name>richcreamerybutter</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Is the year represented by the number of years after 2000 (with the tuna exception)? I notice that "Y" on this chart is usually 1, 2, 3, or 4. God forbid you find something in a bodega manufactured in 1999 - how would this work?</p>]]>
    </content>
    <published>2008-12-30T22:24:22Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9733232</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9733232" />
    <title>Comment from LazyNinja on 2008-12-30</title>
    <author>
        <name>LazyNinja</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>The Julian Code system is no longer used on the majority of Kraft products anymore. They haven't been used since 2003 and are now only used on pizza and some baking goods like Bakers chocolate and some Lu Biscuit products made in Europe. I'm a customer service rep for Kraft Foods, the company now uses a clear Day-Month-Year format for American products and Year-Month-Day for Canadian products.</p>]]>
    </content>
    <published>2008-12-30T22:12:52Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9732691</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9732691" />
    <title>Comment from CityGuySailing on 2008-12-30</title>
    <author>
        <name>CityGuySailing</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>Those amongst you that have never been in a food warehoure or shipping depot ask why dates are not standardized. I would assume that many of you have some form of college education. That is NOT the case for the workers in the warehouses (for the most part). A Julian date makes the math simpler - and STILL mistakes happen. The dates on the cans, boxes, and crates are not PRIMARILY for the consumers, but for the sorting and picking in the warehouses and depots. The guys in there try to ship out the LEAST fresh off the manufacturing lines to get it out of their inventories and into the warehouses of the stores, and then their warehouse workers try to get it onto the trucks to the stores before the expirations run out as well.</p></p>]]>
    </content>
    <published>2008-12-30T21:52:03Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9732488</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9732488" />
    <title>Comment from SacraBos on 2008-12-30</title>
    <author>
        <name>SacraBos</name>
        <uri>http://www.sacrabos.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.sacrabos.com">
        <![CDATA[<p>Wouldn't Sour Cream have a "Best After" date?</p>]]>
    </content>
    <published>2008-12-30T21:44:24Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9732245</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9732245" />
    <title>Comment from Xkeeper on 2008-12-30</title>
    <author>
        <name>Xkeeper</name>
        <uri>n/a</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="n/a">
        <![CDATA[<p><p>@<a href="#c9730445" rel="nofollow">CityGuySailing</a>: <br /><br />
Not only that, but you can write "Jun 27 2008" in a variety of different orders and it will always mean the exact same thing.</p><br />
<p>That and it's only one letter larger than all-numerics.</p></p>]]>
    </content>
    <published>2008-12-30T21:33:41Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9732046</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9732046" />
    <title>Comment from lannister80 on 2008-12-30</title>
    <author>
        <name>lannister80</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9730445" rel="nofollow">CityGuySailing</a>: I don't know of any date format in common use that has a Julian date in it.  When was the last time someone in any country referred to a Julian date in a typical conversation?  "Was last Friday the 315th?"</p>
<p>12252008 and 25122008 I can understand (Dec 25th), but a Julian date?  WHY?</p>]]>
    </content>
    <published>2008-12-30T21:24:58Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9731944</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9731944" />
    <title>Comment from ZekeSulastin on 2008-12-30</title>
    <author>
        <name>ZekeSulastin</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9730445" rel="nofollow">CityGuySailing</a>: ... which is precisely why an international standards group came up with an international standard date format for this sort of thing.</p>]]>
    </content>
    <published>2008-12-30T21:20:36Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9731813</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9731813" />
    <title>Comment from Ein2015 on 2008-12-30</title>
    <author>
        <name>Ein2015</name>
        <uri>http://</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://">
        <![CDATA[<p>@<a href="#c9730268" rel="nofollow">all4jcvette</a>: Thank you for this!</p>]]>
    </content>
    <published>2008-12-30T21:14:24Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9731804</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9731804" />
    <title>Comment from Ein2015 on 2008-12-30</title>
    <author>
        <name>Ein2015</name>
        <uri>http://</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://">
        <![CDATA[<p>@<a href="#c9729808" rel="nofollow">HogwartsAlum</a>: Agreed.</p>
<p>Somebody give the man a star!</p>]]>
    </content>
    <published>2008-12-30T21:14:03Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9731790</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9731790" />
    <title>Comment from Ein2015 on 2008-12-30</title>
    <author>
        <name>Ein2015</name>
        <uri>http://</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://">
        <![CDATA[<p>@<a href="#c9730127" rel="nofollow">ChristopherDavis</a>: Not really, have you seen how many characters are on a label?</p>]]>
    </content>
    <published>2008-12-30T21:13:33Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9731751</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9731751" />
    <title>Comment from Ein2015 on 2008-12-30</title>
    <author>
        <name>Ein2015</name>
        <uri>http://</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://">
        <![CDATA[<p>@<a href="#c9731598" rel="nofollow">thrashanddestroy</a>: Clever morning pun...</p>]]>
    </content>
    <published>2008-12-30T21:11:58Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9731645</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9731645" />
    <title>Comment from RogueSophist on 2008-12-30</title>
    <author>
        <name>RogueSophist</name>
        <uri>n/a</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="n/a">
        <![CDATA[<p>@<a href="#c9731366" rel="nofollow">Rob Weddle</a>: Wait a minute, this seems less like helpful advice and more like...preaching! Nah, I must just be cranky this morning and reading into things. <i>Surely</i> you wouldn't do that to us before noon.</p>]]>
    </content>
    <published>2008-12-30T21:07:30Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9731598</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9731598" />
    <title>Comment from thrashanddestroy on 2008-12-30</title>
    <author>
        <name>thrashanddestroy</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9729652" rel="nofollow">VereKlimchuck</a>: Companies are picking up on that in the states, thankfully. Some still have that "sell by" nonsense, insisting you still have a couple days to use it after the date but I wont play that guessing game.</p>
<p>Egg Beaters, a staple of my breakfast, switched over to the "Use By" date. Why everyone else hasn't, beats me.</p>]]>
    </content>
    <published>2008-12-30T21:05:23Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9731366</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9731366" />
    <title>Comment from Rob Weddle on 2008-12-30</title>
    <author>
        <name>Rob Weddle</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Want help with decoding expiration dates on food containers?  I have a better tip:</p>
<p>Stop buying processed food.</p>
<p>See this apple?  It's red, crisp, firm.  Still edible.  Soft, brown, stinky?  Expired.</p>]]>
    </content>
    <published>2008-12-30T20:52:12Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9731324</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9731324" />
    <title>Comment from maciejb on 2008-12-30</title>
    <author>
        <name>maciejb</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Honestly, I think a lot of this comes from using old equipment and trying to squeeze as much as possible in as few characters. At the plant I work at, we only have 8-digit stamps at most lines. We use a format like 2008DE30, and that's stamped near a pre-printed area where it says "Best Before". Not too confusing.. but I can definitely understand the "that's the way we've always done it" mentality. We got new printers on a few of our lines which are far less limited. We could write a few full sentences on the side of the box if we wanted to. What do you think we do? 2008DE30, of course, because that's the way we've always done it. It's a lot less painful to just keep doing what you're doing, than it is to start putting in all the paperwork, getting all the sales people involved (ugh! sales people), etc, etc. Yeah, exceptional organizations have better cultures to handle change, but most organizations are not exceptional.</p>]]>
    </content>
    <published>2008-12-30T20:50:20Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9731027</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9731027" />
    <title>Comment from zentex on 2008-12-30</title>
    <author>
        <name>zentex</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>where is the key for Month Code #2?</p>]]>
    </content>
    <published>2008-12-30T20:36:47Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730899</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730899" />
    <title>Comment from Applekid on 2008-12-30</title>
    <author>
        <name>Applekid</name>
        <uri>http://</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9730445" rel="nofollow">CityGuySailing</a>: Different countries have different labeling requirements for food. They can get THAT right because it's mandated by law: why is it all of a sudden so hard to localize a date to an area based on this data?</p></p>]]>
    </content>
    <published>2008-12-30T20:30:51Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730639</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730639" />
    <title>Comment from OprahBabb on 2008-12-30</title>
    <author>
        <name>OprahBabb</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I'd rather try my luck with the labels than read that chart.  Holy sheet mayne wtf.</p>]]>
    </content>
    <published>2008-12-30T20:18:06Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730487</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730487" />
    <title>Comment from Alex Jarvis on 2008-12-30</title>
    <author>
        <name>Alex Jarvis</name>
        <uri>http://www.alxjrvs.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.alxjrvs.com">
        <![CDATA[<p>@<a href="#c9730445" rel="nofollow">CityGuySailing</a>: I can understand using an internal code, but by asking someone to use the specific day on the Julian Calendar? at least print the expiration date in an easier to read format, [insert companies here]</p>]]>
    </content>
    <published>2008-12-30T20:09:13Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730445</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730445" />
    <title>Comment from CityGuySailing on 2008-12-30</title>
    <author>
        <name>CityGuySailing</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>About dates: My point being, that even across countries, date formats vary. Corporations can hardly be faulted for having a code of their own that THEY understand (and train their personnel up to) across international boundaries. Disclaimer: I worked for a mega-large food company in the 80's.</p></p>]]>
    </content>
    <published>2008-12-30T20:07:21Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730379</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730379" />
    <title>Comment from BeyondtheTech on 2008-12-30</title>
    <author>
        <name>BeyondtheTech</name>
        <uri>http://www.beyondthetech.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.beyondthetech.com">
        <![CDATA[<p>Someone needs to step in and get this in order.  FDA?  FTC?  FBI?!</p>]]>
    </content>
    <published>2008-12-30T20:04:37Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730281</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730281" />
    <title>Comment from pz on 2008-12-30</title>
    <author>
        <name>pz</name>
        <uri>http://mdm-adph.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://mdm-adph.blogspot.com">
        <![CDATA[<p>Remind me to stock up on "Beef Hash" for the coming apocalypse.  That shit's got some shelf life, jeebus.</p>]]>
    </content>
    <published>2008-12-30T19:58:49Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730268</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730268" />
    <title>Comment from all4jcvette on 2008-12-30</title>
    <author>
        <name>all4jcvette</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>What is a Julian Date:<br /><a href="http://aa.usno.navy.mil/data/docs/JulianDate.php" rel="nofollow">[aa.usno.navy.mil]</a> <br /><a href="http://en.wikipedia.org/wiki/Julian_day" rel="nofollow">[en.wikipedia.org]</a><br />Enjoy</p></p>]]>
    </content>
    <published>2008-12-30T19:58:17Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730218</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730218" />
    <title>Comment from smallestmills on 2008-12-30</title>
    <author>
        <name>smallestmills</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I once worked at World Market and we had a 6 inch binder with each vendor on a page with keys to all the different codes.  What I did learn was it was up with the company to work with the vendors in order to get them to put a date on the item as opposed to a code.  They did a pretty good job, in the 4 years that I worked there almost all their vendors changed from codes to dates.  These were bigger brands, too, such as Cadbury, Lindt, and Ghiradelli.</p>]]>
    </content>
    <published>2008-12-30T19:54:43Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730187</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730187" />
    <title>Comment from socialSTD on 2008-12-30</title>
    <author>
        <name>socialSTD</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9730032" rel="nofollow">CityGuySailing</a>:</p>
<p>True, but it's still easier to tell retailers that the code is in mm/dd/yy or dd/mm/yy format. That way you won't need a decoder ring to figure out if your Ovaltine is expired or not.</p>]]>
    </content>
    <published>2008-12-30T19:53:03Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730186</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730186" />
    <title>Comment from morganlh85 on 2008-12-30</title>
    <author>
        <name>morganlh85</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9729536" rel="nofollow">shorty63136</a>: There is a little key at the bottom.</p>]]>
    </content>
    <published>2008-12-30T19:52:50Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730179</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730179" />
    <title>Comment from snowburnt on 2008-12-30</title>
    <author>
        <name>snowburnt</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9730032" rel="nofollow">CityGuySailing</a>: don't they do DD/MM/YYYY in Europe?  Makes a lot more sense than doing MM/DD/YYYY...</p>]]>
    </content>
    <published>2008-12-30T19:52:23Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730127</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730127" />
    <title>Comment from ChristopherDavis on 2008-12-30</title>
    <author>
        <name>ChristopherDavis</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9730032" rel="nofollow">CityGuySailing</a>: This is true, but there's an ISO standard format for dates for a reason. (YYYY-MM-DD, which has advantages including being able to be sorted lexically as well as being unambiguous.) Unfortunately, 10 characters is a lot of space to take up on a food label just for a date.</p>]]>
    </content>
    <published>2008-12-30T19:50:08Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730119</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730119" />
    <title>Comment from JohnDeere on 2008-12-30</title>
    <author>
        <name>JohnDeere</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9729887" rel="nofollow">socialSTD</a>: they would lose sales. if you cant read it you dont know its went bad and you buy it anyway.</p></p>]]>
    </content>
    <published>2008-12-30T19:49:45Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730098</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730098" />
    <title>Comment from Persistence on 2008-12-30</title>
    <author>
        <name>Persistence</name>
        <uri>http://</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9729887" rel="nofollow">socialSTD</a>: That would make too much sense/be too simple. I suppose those at the top have to justify working in an extension of the "food service" industry by making things more complex.</p><br />
<p>This just makes me wonder how much food is wasted because of these complex systems of timekeeping. It would make more sense to put the date in hexidecimal or binary than to use yet another system (that's not taught in school).</p><br />
<p>This just chaps my ass! The more I learn, the more I understand that primary and high schools don't teach but a small fraction of the shit you actually need to know when you get out in the working world! They don't even give you a good foundation (even less now than when I went to school). /rant</p></p>]]>
    </content>
    <published>2008-12-30T19:48:56Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730032</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730032" />
    <title>Comment from CityGuySailing on 2008-12-30</title>
    <author>
        <name>CityGuySailing</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9729887" rel="nofollow">socialSTD</a>: Internationally, date formats are not consistant.</p></p>]]>
    </content>
    <published>2008-12-30T19:45:41Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9730010</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9730010" />
    <title>Comment from CityGuySailing on 2008-12-30</title>
    <author>
        <name>CityGuySailing</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p><p>@<a href="http://consumerist.com/5120395/cheat-sheet-for-sketchy-food-expiration-codes#c9729577" rel="nofollow">OmniZero</a>: Actually, today is 365. Thou hast forgotten about the Leap Year.</p></p>]]>
    </content>
    <published>2008-12-30T19:44:42Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9729887</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9729887" />
    <title>Comment from socialSTD on 2008-12-30</title>
    <author>
        <name>socialSTD</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>And why can't manufacturers put the expiration date in a common format (mm/dd/yy)?</p>]]>
    </content>
    <published>2008-12-30T19:38:17Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9729808</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9729808" />
    <title>Comment from HogwartsAlum on 2008-12-30</title>
    <author>
        <name>HogwartsAlum</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>This is awesome.  <br />
Thanks Brian, and thanks to everyone for explaining the Julian date thing.</p>]]>
    </content>
    <published>2008-12-30T19:34:00Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9729696</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9729696" />
    <title>Comment from shorty63136 on 2008-12-30</title>
    <author>
        <name>shorty63136</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9729577" rel="nofollow">OmniZero</a> &amp; @<a href="#c9729612" rel="nofollow">cynical_bastard</a>: Awesome. Thanks. :)</p>]]>
    </content>
    <published>2008-12-30T19:27:06Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9729652</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9729652" />
    <title>Comment from Anonymous on 2008-12-30</title>
    <author>
        <name>Anonymous</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>The UK system seems to be slightly easier to understand. Every item of food has "Use By End  " printed on it. By law.
Any questions?</p>]]>
    </content>
    <published>2008-12-30T19:24:19Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9729612</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9729612" />
    <title>Comment from cynical_bastard on 2008-12-30</title>
    <author>
        <name>cynical_bastard</name>
        <uri>http://</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://">
        <![CDATA[<p>@<a href="#c9729536" rel="nofollow">shorty63136</a>: Julian Day Numbers<br />
by Peter Meyer</p>
<p><a href="http://www.hermetic.ch/cal_stud/jdn.htm" rel="nofollow">[www.hermetic.ch]</a></p>]]>
    </content>
    <published>2008-12-30T19:21:08Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9729577</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9729577" />
    <title>Comment from OmniZero on 2008-12-30</title>
    <author>
        <name>OmniZero</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@<a href="#c9729536" rel="nofollow">shorty63136</a>: The actual day of the year. Like today, December 30th, is the 364th day of the year.</p>]]>
    </content>
    <published>2008-12-30T19:17:53Z</published>
  </entry>

  <entry>
    <id>tag:64.14.177.195,2008://1.5120395-comment:9729536</id>
    <thr:in-reply-to ref="tag:64.14.177.195,2008://1.5120395" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html"/>
    <link rel="alternate" type="text/html" href="http://consumerist.com/2008/12/cheat-sheet-for-sketchy-food-expiration-codes.html#c9729536" />
    <title>Comment from shorty63136 on 2008-12-30</title>
    <author>
        <name>shorty63136</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Oh wow. This is pretty handy.</p>
<p>Anybody know what a Julian date is though?</p>]]>
    </content>
    <published>2008-12-30T19:14:48Z</published>
  </entry>


</feed>



