Another work week starts with me waiting for the bus back home from band practice. Waiting on the corner of 45th and University Way in front of Pier 1 imports, I notice that they have a display selling "Year 2000 calendars". No one would ever be selling "Year 1999 Calendars". I guess they didn't want people to get confused and think they were Lever 2000 calendars, or 2000 flushes calendars, or just 5.4644808743169398907103825136612 calendars for every day of the coming leap year.

Once an irc friend of mine noted my "Naive code" when I did current date calculations using if(year%4) monthlenth[1]=29; because of the "hundred year rule" of the gregorian system under which years evenly divisable by 100 are excepted from the rule, bringing average year length to 365.24 days (the exact time it takes for the earth to circle the sun is 365.2422 days). What he didn't realize is that there is also a "400 year rule", which states that years evenly divisable by 400 are an exception to the exception and thus ARE leap years making average year length 365.2425 and making my code safe until someone tries to use it in february 2100, at which time it will have hopefully undergone revision. The last time the 100 year rule was in effect, Leon Trotsky was a spry lad of 20 (Today is actually his birthday. Happy 120th, you wacky Red-Army organizing exile.). The last time the 400 year rule was in effect, I guess it was the Italian rennaissance. Well, so suggests Brett, who is taking intensive Italian right now.

Brett also notes that "panini" is Italian for "sandwiches", so when you order a "Panini Sandwich", in Italian you would be literally sounding like a complete fool.

Even with the 400 year rule, we still gain a day every 3300 years or so, at which time we'll have an 3300 year leap exception to the 100 year rule. Maybe we'll have a leap year with 30 days in february or something.

Huhhhhh gubluh. I can't tell if I typed an equals or a hyphen between disk and validator, my vision is going double, vertically. I'm taking a little break from the usual steady stream of work right now, which is why I'm not working.

Bug found in scheduler. Film at 11. --Jargon.txt

That pretty much summarizes what I think of Y2K related computer issues. So, you let a bunch of really cheap business programmers write your business software in the mid 80s and now it's going to get terminally confused because it was using an abbreviated form of the year as a value for comparison? Well, duh, ralph! COBOL leads to suffering, goes without saying!! You almost have to specifically try to be naive in order for Y2K matter to a C program.

Wuh oh, that beeping is the smoke alarm, which means that what I was cooking an hour ago is now ruined because I forgot about it.

And it looks like I seriously wrote that I'm not working because I'm not working.