sergebroom | no news not necessarily good news and can be a broken newsline

Last night, I left to the local SF club's monthly meeting less than 30 minutes before the official start. Why such an in extremis departure? Remember my Big Project of these last few weeks and the deployment of the upgraded job flow? Friday night was the first time that the monthly job flow was to run, and I didn't want to step away until I had a warm and fuzzy feeling that I would not be called while at the club meeting.

By the time the meeting was over at 10pm, my cell phone had not gone off with a call for the team's on-duty person. Still, as soon as I was home, I logged in to do some monitoring. And immediately found that one crucial job had failed right after I had left. And that our oncall person didn't know about it because the automated failure-notification job had run but that its message had not reached my co-worker.

Two hours later, we had made sure that the failure (which was not related to my Project) was resolved.

No news is not not necessarily good news.
It can be a broken newsline.
Oh well.

I had a good time at the club's meeting. Yvonne Coates, a local writer, read excerpts from stories she's working on. And there was a sampling of desserts. Automobile-related puns were briefly uttered, but none by yours truly, as I was on my best behavior. I also found my name mentionned in the club's newsletter's recap of the year, although it was as a member of the team that had lost June's Outburst competition.