Arg

October 31st, 2004

Twenty minutes ago, I woke up with a start and looked at my clock. “6:23” it said. The alarm should have gone off three minutes earlier — man, was I lucky to wake up on my own!

I got up, took a shower, and came back to my room. I was about to get dressed to go to work when I noticed that I had very few clean clothes handy. “That’s odd, I must have forgotten to do laundry on Sunday,” I thought. “Wait a second… I don’t remember doing anything on Sunday.” Suspicious, I ran to the computer and checked the computer’s clock. “Sunday, October 31, 2004” it said. D’oh! Needless to say, I felt stupid.

Meh. I think I’ll go back to sleep.

  1. Keacher
    October 31st, 2004 at 10:22 | #1

    It turns out that it was even worse, because I forgot to change my clock for the end of daylight saving time. That means I really got up at *5:23* a.m. Ug!

  2. October 31st, 2004 at 20:34 | #2

    I’m disappointed Keacher, I thought it would take at least 6 months for the corporate world to completely take over your life…

  3. jimmers
    November 1st, 2004 at 20:14 | #3

    maybe it’s all that high-buck booze marinating you. (this is of course in reference to your fine booze collection.) do you drink that stuff?

  4. November 2nd, 2004 at 01:18 | #4

    I heard all that high grade alcohol is still burried in a box, aptly marked “BoOZe”.

    On a different note, what’s up with the different comment header for the first comment on each post?

  5. Keacher
    November 2nd, 2004 at 06:39 | #5

    Yes, on rare occasions, I do drink some of it. It’s finally been moved out of the “Booze” box and onto a shelf.

    Not sure about the comment header; the first comment looks exactly the same as the second and subsequent comments in both IE6 and Firefox.

  6. November 2nd, 2004 at 16:06 | #6

    Firefox 1.0 PR in Windoze.

  7. November 2nd, 2004 at 16:09 | #7
  8. Keacher
    November 2nd, 2004 at 16:36 | #8

    Strange. I don’t see that behavior here at the office (Firefox 1.0 PR), either.

    Hmmm…

  9. November 3rd, 2004 at 10:46 | #9

    Looks like it does it on first load, then a reload fixes it. Probably chalk it up to some sort of Mozilla bug.

  10. Keacher
    November 11th, 2004 at 08:37 | #10

    I found the source of the problem. It should be fixed now.

Comments are closed.