Spreading panic...

If you're a fan of Castle, don't like spoilers, and haven't watched the show these past couple of weeks, you might want to skip this post.

During this past Monday's adventure, Castle gets back to his apartment and tells his mother and daughter to get out of Manhattan immediately because of some impending gynormous threat. Daughter Alexis picks up her phone and starts dialing. Castle stops her; she protests, saying she has to warn her boyfriend. Castle argues compellingly that doing so would almost certainly cause BF or his family to call someone else, and before you'd know it, a panic would be under way. Alexis reluctantly agrees to not call her BF, at which point the two women go out the door.

So am I right in thinking (to the extent that I realize this is based on my reaction to fiction) that Alexis's relationship with her BF is now doomed because she didn't call? (I mean, the way the relationship has been developed in the series, the BF is Alexis's "first love," which statistically doesn't bode well for any kind of permanence to begin with.) To my way of thinking—call it an analysis of plausible behavior—wouldn't guilt necessarily be the result of not having called (despite the fact that, in the end, the threat was nullified)?

Of course, life is complicated, as are people, so all of this is idle speculation. Having said that, it'd be interesting to write a scene in which, say, Alexis tries to apologize to the BF. (Gulp! Have I just exhibited an interest in writing fanfiction?)

Cheers...

Just sayin'...

I still have the default newsreader widgets on my DROID X and browse them at odd moments, like when I'm waiting for water to boil for tea.

Yesterday, I was surprised to see several items announcing that (a) Charlie Sheen had joined Twitter and (b) he had amassed half a million "followers" in short order.

This is news? (Then again, perhaps it is, but not in the sense intended by those reporting it.)

There are times I cry for my species, and for its future prospects.

Cheers...

Trying to go with the flow...

Lately, whenever my cell phone is either not hitting the local tower or if I don't pick up the phone, Verizon has started to inform callers that my number has either been "changed, disconnected, or no longer in service." I should have paid attention instead of writing it off as a random glitch the first time someone told me this happened.

The seriousness of this situation was brought home to me rather dramatically today when a client I haven't done work for in about two years tried to call and inquire about my availability for a huge job (which I may still land, except that the end client may have already found someone else to do the work).

Anyway, I just spent a somewhat interesting half hour on the phone with Verizon customer support and technical support. There was a problem, and by the time I hung up the phone, the problem appeared to have gone away.

While on hold, I decided to buy a trial subscription for a Skype call-in number, which will mean having Skype up all the time (and probably on a dedicated computer, as incoming calls will not come in through Skype Mobile on my cell phone), but as I am not so affluent as to remain inaccessible to my clients, I think it is a good investment. (I also got a Google Voice number, but when anyone calls that number, the service apparently routes the call through to a number that one must answer, and as my only available number is my cell phone, it's not really a solution.)

Now, to keep my fingers crossed about the job. Hopefully, the technical level of the text will be high enough to scare other prospective candidates until my hat goes in the ring tomorrow morning.

In the meantime, perhaps I should go eat dinner.

Cheers...