<?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: How to Become a Human Calendar</title>
	<atom:link href="http://litemind.com/how-to-become-a-human-calendar/feed/" rel="self" type="application/rss+xml" />
	<link>http://litemind.com/how-to-become-a-human-calendar/</link>
	<description>Exploring ways to use our minds efficiently.</description>
	<lastBuildDate>Fri, 06 Nov 2009 19:19:17 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Luciano Passuello</title>
		<link>http://litemind.com/how-to-become-a-human-calendar/#comment-40084</link>
		<dc:creator>Luciano Passuello</dc:creator>
		<pubDate>Sat, 10 Oct 2009 14:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://litemind.com/how-to-become-a-human-calendar/#comment-40084</guid>
		<description>Hi Jason,

The part you got it wrong is that 99 mod 7 is not 14, but 1. &lt;em&gt;MOD&lt;/em&gt; is the remainder of the division, not the quotient (that would be &lt;em&gt;DIV&lt;/em&gt;)... I used to get it wrong all the time, too! :)</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->Hi Jason,</p>
<p>The part you got it wrong is that 99 mod 7 is not 14, but 1. <em>MOD</em> is the remainder of the division, not the quotient (that would be <em>DIV</em>)&#8230; I used to get it wrong all the time, too! <img src='http://litemind.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> <!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://litemind.com/how-to-become-a-human-calendar/#comment-40081</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Sat, 10 Oct 2009 14:05:48 +0000</pubDate>
		<guid isPermaLink="false">http://litemind.com/how-to-become-a-human-calendar/#comment-40081</guid>
		<description>I saw this and got really excited, but I can&#039;t figure out where I&#039;m going wrong with July 4, 1776. (4+76+(76/4)) = 99 mod 7  is 14 so year code is 2. (2+0+4) = 6 So it should be a friday, but it&#039;s a thursday. I don&#039;t see where I&#039;m going wrong.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->I saw this and got really excited, but I can&#8217;t figure out where I&#8217;m going wrong with July 4, 1776. (4+76+(76/4)) = 99 mod 7  is 14 so year code is 2. (2+0+4) = 6 So it should be a friday, but it&#8217;s a thursday. I don&#8217;t see where I&#8217;m going wrong.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mati</title>
		<link>http://litemind.com/how-to-become-a-human-calendar/#comment-39970</link>
		<dc:creator>Mati</dc:creator>
		<pubDate>Fri, 09 Oct 2009 00:50:43 +0000</pubDate>
		<guid isPermaLink="false">http://litemind.com/how-to-become-a-human-calendar/#comment-39970</guid>
		<description>This technique is awesome...
I only learned it for fun but then I discovered is far more useful...
I use it for example to know the thursdays of a particular month...
Just having the first day of the month and adding 7..
Really, It&#039;s useful. Thanks for sharing it, man =)</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->This technique is awesome&#8230;<br />
I only learned it for fun but then I discovered is far more useful&#8230;<br />
I use it for example to know the thursdays of a particular month&#8230;<br />
Just having the first day of the month and adding 7..<br />
Really, It&#8217;s useful. Thanks for sharing it, man =)<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Trackbacks for How to Become a Human Calendar [litemind.com] on Topsy.com</title>
		<link>http://litemind.com/how-to-become-a-human-calendar/#comment-37791</link>
		<dc:creator>Twitter Trackbacks for How to Become a Human Calendar [litemind.com] on Topsy.com</dc:creator>
		<pubDate>Tue, 01 Sep 2009 16:13:58 +0000</pubDate>
		<guid isPermaLink="false">http://litemind.com/how-to-become-a-human-calendar/#comment-37791</guid>
		<description>[...] How to Become a Human Calendar  litemind.com/how-to-become-a-human-calendar &#8211; view page &#8211; cached  Exploring ways to use our minds efficiently., Mentally finding out the day of the week for any date is a skill you can easily learn. You don&#039;t need to be an autistic genius – all it takes is basic memorization effort and some trivial math. &#8212; From the page [...]</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->[...] How to Become a Human Calendar  litemind.com/how-to-become-a-human-calendar &ndash; view page &ndash; cached  Exploring ways to use our minds efficiently., Mentally finding out the day of the week for any date is a skill you can easily learn. You don&#39;t need to be an autistic genius – all it takes is basic memorization effort and some trivial math. &mdash; From the page [...]<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luciano Passuello</title>
		<link>http://litemind.com/how-to-become-a-human-calendar/#comment-37763</link>
		<dc:creator>Luciano Passuello</dc:creator>
		<pubDate>Mon, 31 Aug 2009 23:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://litemind.com/how-to-become-a-human-calendar/#comment-37763</guid>
		<description>I had no idea how the system I described here could be derived. Thanks for that --- it&#039;s a brilliant piece of reasoning you got there, Jason.  &lt;strong&gt;I&#039;m delighted to see how you created a &quot;meta system&quot; for calculating dates!&lt;/strong&gt;

Your method of &#039;rolling back&#039; digits is also very ingenious. It seems that it&#039;s great to calculate dates that span multiple years (it makes it easy to calculate dates two, three or many years ahead or behind). 

The method I describe here --- at least the way I use it --- is great for calculating dates in a &lt;em&gt;particular year&lt;/em&gt; --- for example, the year we&#039;re on. The month codes, although arbitrary, are &lt;em&gt;always&lt;/em&gt; the same and, as such, become so second-nature that, in fact, there&#039;s only one number left to memorize each year.

I&#039;m saving your method for my own reference and future experiments. 
&lt;strong&gt;Thank you so much for the fresh new look to the calendar method! &lt;/strong&gt;</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->I had no idea how the system I described here could be derived. Thanks for that &#8212; it&#8217;s a brilliant piece of reasoning you got there, Jason.  <strong>I&#8217;m delighted to see how you created a &#8220;meta system&#8221; for calculating dates!</strong></p>
<p>Your method of &#8216;rolling back&#8217; digits is also very ingenious. It seems that it&#8217;s great to calculate dates that span multiple years (it makes it easy to calculate dates two, three or many years ahead or behind). </p>
<p>The method I describe here &#8212; at least the way I use it &#8212; is great for calculating dates in a <em>particular year</em> &#8212; for example, the year we&#8217;re on. The month codes, although arbitrary, are <em>always</em> the same and, as such, become so second-nature that, in fact, there&#8217;s only one number left to memorize each year.</p>
<p>I&#8217;m saving your method for my own reference and future experiments.<br />
<strong>Thank you so much for the fresh new look to the calendar method! </strong><!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://litemind.com/how-to-become-a-human-calendar/#comment-37685</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Sun, 30 Aug 2009 18:03:18 +0000</pubDate>
		<guid isPermaLink="false">http://litemind.com/how-to-become-a-human-calendar/#comment-37685</guid>
		<description>Hi, Luciano just found your blog the other day. Some really great stuff on here.

I started writing a comment a little while ago explaining another method of being able to figure out dates. By the time I got to the end of it I realized that formula you gave could be derived from the method that I used.

The whole thing got kind of long so I wrote it up over here if you&#039;re interested:
http://jason-somuchtodo.blogspot.com/2009/08/mathematical-diversion-calculating.html

It also explains why you and Melissa can use different month codes and how you can adjust the whole thing to get monday=1 (actually that&#039;s not how I did it but you can) plus making it easier so you don&#039;t have to memorize year codes but just calculate them easily on the spot.

I wrote the whole thing off the top of my head so it&#039;s not terribly well organized but you should be able to follow it.

Of course if you already know where the whole thing is derived from then you won&#039;t find anything knew in what I&#039;ve written. But anyway...</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->Hi, Luciano just found your blog the other day. Some really great stuff on here.</p>
<p>I started writing a comment a little while ago explaining another method of being able to figure out dates. By the time I got to the end of it I realized that formula you gave could be derived from the method that I used.</p>
<p>The whole thing got kind of long so I wrote it up over here if you&#8217;re interested:<br />
<a href="http://jason-somuchtodo.blogspot.com/2009/08/mathematical-diversion-calculating.html" rel="nofollow">http://jason-somuchtodo.blogsp.....ating.html</a></p>
<p>It also explains why you and Melissa can use different month codes and how you can adjust the whole thing to get monday=1 (actually that&#8217;s not how I did it but you can) plus making it easier so you don&#8217;t have to memorize year codes but just calculate them easily on the spot.</p>
<p>I wrote the whole thing off the top of my head so it&#8217;s not terribly well organized but you should be able to follow it.</p>
<p>Of course if you already know where the whole thing is derived from then you won&#8217;t find anything knew in what I&#8217;ve written. But anyway&#8230;<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How To: 121 Ways to Increase Brain Power &#124; Cogent Nirvana</title>
		<link>http://litemind.com/how-to-become-a-human-calendar/#comment-37400</link>
		<dc:creator>How To: 121 Ways to Increase Brain Power &#124; Cogent Nirvana</dc:creator>
		<pubDate>Wed, 26 Aug 2009 18:09:14 +0000</pubDate>
		<guid isPermaLink="false">http://litemind.com/how-to-become-a-human-calendar/#comment-37400</guid>
		<description>[...] Dump the calendar! [...]</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->[...] Dump the calendar! [...]<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luciano Passuello</title>
		<link>http://litemind.com/how-to-become-a-human-calendar/#comment-37037</link>
		<dc:creator>Luciano Passuello</dc:creator>
		<pubDate>Thu, 20 Aug 2009 15:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://litemind.com/how-to-become-a-human-calendar/#comment-37037</guid>
		<description>Nice explanation, John. You threw in some interesting tips on how to make sense of the leap year adjustment idea. 

Just a quick reminder: &lt;em&gt;the adjustment is only necessary for the months of January and February&lt;/em&gt;. Calculations for the other months behave just as in all other years.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->Nice explanation, John. You threw in some interesting tips on how to make sense of the leap year adjustment idea. </p>
<p>Just a quick reminder: <em>the adjustment is only necessary for the months of January and February</em>. Calculations for the other months behave just as in all other years.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luciano Passuello</title>
		<link>http://litemind.com/how-to-become-a-human-calendar/#comment-37036</link>
		<dc:creator>Luciano Passuello</dc:creator>
		<pubDate>Thu, 20 Aug 2009 14:53:55 +0000</pubDate>
		<guid isPermaLink="false">http://litemind.com/how-to-become-a-human-calendar/#comment-37036</guid>
		<description>It&#039;s interesting to see how different people prefer different balances between mental calculations and memorization. 

Fortunately, the technique is flexible enough to allow tradeoffs at different points. The more numbers you are willing to memorize --- that is, the more effort you&#039;re willing to put upfront --- the faster each calculation will be. 

These are the same tradeoffs we often see in computing, such as &#039;processing power&#039; vs. &#039;storage space&#039; --- and, just as those, there&#039;s never an ultimate answer. 

Thanks for sharing!</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->It&#8217;s interesting to see how different people prefer different balances between mental calculations and memorization. </p>
<p>Fortunately, the technique is flexible enough to allow tradeoffs at different points. The more numbers you are willing to memorize &#8212; that is, the more effort you&#8217;re willing to put upfront &#8212; the faster each calculation will be. </p>
<p>These are the same tradeoffs we often see in computing, such as &#8216;processing power&#8217; vs. &#8217;storage space&#8217; &#8212; and, just as those, there&#8217;s never an ultimate answer. </p>
<p>Thanks for sharing!<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john</title>
		<link>http://litemind.com/how-to-become-a-human-calendar/#comment-37035</link>
		<dc:creator>john</dc:creator>
		<pubDate>Thu, 20 Aug 2009 14:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://litemind.com/how-to-become-a-human-calendar/#comment-37035</guid>
		<description>For a leap year you have to subtract one from your result.
Let’s say you have the date February 14 1976. You know the code for February is 4. 14 is zero, and 1976 is code number 4. 

4+0+4=8, but you have to subtract one for the leap year.  8 minus 1 is 7, which equals 0. (Saturday)

You can always look at the day in the leap year as one less than the original.  So if you have to figure out the date for January 15, 2008, just think of January 14th instead. 

Another way to practice this is to look at the present century.  I was born on a Friday. But my birthday for the same date in this century will be on a Thursday.  That means that the entire code structure will be one day off for this century. So I do the same thing for dates in this century.  I subtract one from the number from the final result.  May 26, 1992 was (2+26+3=31) Tuesday.  Therefore May 26, 2092 will be on a Monday.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->For a leap year you have to subtract one from your result.<br />
Let’s say you have the date February 14 1976. You know the code for February is 4. 14 is zero, and 1976 is code number 4. </p>
<p>4+0+4=8, but you have to subtract one for the leap year.  8 minus 1 is 7, which equals 0. (Saturday)</p>
<p>You can always look at the day in the leap year as one less than the original.  So if you have to figure out the date for January 15, 2008, just think of January 14th instead. </p>
<p>Another way to practice this is to look at the present century.  I was born on a Friday. But my birthday for the same date in this century will be on a Thursday.  That means that the entire code structure will be one day off for this century. So I do the same thing for dates in this century.  I subtract one from the number from the final result.  May 26, 1992 was (2+26+3=31) Tuesday.  Therefore May 26, 2092 will be on a Monday.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
</channel>
</rss>
