Sunday, September 26, 2004

9/26/2004 - Status Update

In my quest to become able to charm the most unattainable of women, I must provide my sexy readers with status updates.

The Waitress At The Bar
This isn't Cindy from Shenanigans. This is another waitress from another place entirely. I went to lunch with my friend Scott last week, and I saw a waitress that just mesmerized me. I'm a sucker for pretty eyes, and she had that. She also had the glasses that I affectionately call Naughty Librarians (S***n had Naughty Librarians, and she knew that I was defenseless against them).

I've never picked up a waitress, but I think I'm going to try. If I take a longshot like that, and I miss, no biggie. Waitresses are practiced in the art of rejecting men, and the good ones can do it in a way that they still get a good tip. "Oh, you're so sweet, but I can't date customers."

So, status on this waitress - incredibly attractive, soft spoken yet confident look about her. Jay walked out without even knowing her name. Jay received 100 Loser Points, redeemable for more one-player video games.

A good status update will identify tasks, issues, and a forward plan.

Task: Ask a waitress out.
Issue: Jay's a dink.
Forward Plan: Jay's going to stop being a dink, and just ask a waitress out.

However, there's a predecessor to asking a woman out. Think of this like software design, fellow software designers. Can you just say that you need to write Woman.AskOut()? Not at all! You need to know the parameters. You need to know the return value. You need to address the design, since you may have to overload this method for different woman types. What other interfaces will a woman have? Don't answer that, dorks - I can hear your snorting laughter from here. Object oriented programmers, insert joke here about women being objects.

So, fellow programmers, riddle me this - can we just call the Woman.AskOut() method without some sort of initialization? I think that it's very likely that the Woman object may have some properties, such as Woman.Receptivity, which may have been set by another application entirely. A Woman is very clearly an out-of-process multi-user component, correct? So we must perform some initialization, otherwise the method call is going to fail, no bones about it.

We need to pass properties about the calling application. Some properties, such as physical attributes, are public properties, which we don't need to pass. Others, such as SenseOfHumor or Confidence, need to be passed during initialization.

I need to think about this for a few days. Nerds and non-nerds, input is appreciated.

1 Comments:

At September 27, 2004 at 11:38 AM, Blogger Bad Penny said...

Jay ~ You are a dork, a dink & a nerd... Any waitress would be LUCKY to get a date with you. Don't think too much though as that frying train-transformer smell can be a turn-off.

 

Post a Comment

<< Home