He’s done it again!

Yes, dear readers, it was a pleasant interlude. But I fear it’s over.

You see, our friend RobotJam has returned from vacation. (And, btw, you need to check out his post dated yesterday. A HILARIOUS story of his experience in a pub in Yorkshire.)

(Speaking of Yorkshire, isn’t that the place that’s named for the pudding?)

While Rob was gone, he managed to avoid dreaming. “*Coincidentally*” during that same period of time there was a strange absence of the events we’ve come to identify as part of the “C.”

(If you’re just visiting and not familiar with the “C,” it stands for a word that starts with “Con” and ends with “piracy.” Oh, there’s an “s” in the middle. But we don’t actually SAY the word aloud or spell it out in its entirety, you see, because that gives it strength.)

When the “C” is active, all sorts of mechanical, electronic/electrical, plumbing, structural, and other types of failures occur. And they usually occur in series. And parallel failures occur among others of us who understand this phenomenon.

Why do I think the interlude is over, you ask?

I have a side-by-side refrigerator-freezer, with an ice and cold-water dispenser in the freezer door. Up until Sunday everything worked just fine. Then, (gee, the same day that Rob was back and started blogging again... hmmm...) Carol tried to dispense some cold water.

I’ll bet you think it didn’t work, right? OH, no, it dispensed cold water just fine. Trouble was; when Carol removed the glass the cold water kept on dispensing! She yelled for me to come quick, grabbed a nearby plastic pitcher (larger container) and held it under the flow, while I tried to turn off the water shutoff valve under the kitchen counter.

Now, isn’t it strange that the dispenser mechanism worked fine one day, and then overnight went whacko? Oh! There’s more. This dispenser features a selector that allows you to get ice cubes, crushed ice, or water. Moving the selector to the “cube” position causes the system to produce crushed ice, not cubes. My point: the entire device is now non-responsive.

**SIGH**

Yes, I hear you. You’re asking, “So why is that such a big deal?”

Well, it’s not. But I fear it’s just the beginning. You wait and see if this post doesn’t bring comments from others who have begun to experience a strange “*coincidence*” of similar or somehow related problems or failures.

And I’m still not totally convinced that RobotJam is part of the problem.

(But the timing is certainly suspect! )