Plodding Along

Despite being up somewhat late last night --I was finishing up "The First Elizabeth" by Carolly Erickson, a biography of Elizabeth I. She dies at the end... totally didn't see that coming-- I was up & about fairly early today. There were things to do!

I pushed two loads of laundry through the campground's washer & dryer. Having the facilities here greatly simplified packing: I needed only clothes for a few days rather than, say, ten. As storage space in our trailer is somewhat limited, anything we can do to reduce clutter & bulk has a big impact.

While the laundry was running, I had a shower and made myself as minimally presentable as to not scare off the wildlife, then began catching up on office email from the overnight shift.

My dear employer was scheduled to perform a routine code deployment to the production environments last night. These are seldom pretty events and many times the majority of the fallout and damage isn't apparent until customers begin logging in on Thursday. Since I'm the backup primary on-call, I was expecting to be flooded with frantic debugging requests and calls for assistance, especially in the mid-morning eastern time while the Pacific coast colleagues are in the middle of their early commute to work.

To my surprise, the flood didn't happen as the code deployment was cancelled. I'm not sure if the powers-that-be decided the code wasn't ready for prime-time or if they decided it was too risky to do push new code into production just before everyone vanishes on vacation for Labour Day. In any case, I'm grateful.

Alas, I'm still stymied at the moment on one particular server build. I'd like to use an identical system as a model for my work on this new system but I don't have the passwords for the original. I have to wait for someone to get into the office in California before I can proceed. Hopefully, this minor annoyance of a task will be complete in a couple of hours.

On the good side, my wireless broadband has worked really well. Yeah, I'd like better bandwidth but this is pretty good. My plan has only 250MB/month before surcharges kick in so I've been trying to use it sparingly. Still, three full days of intensive usage has consumed only 70MB thus far so I think I can relax my constraints a little.

kent4str left DC around 10am today so he should be here 4ish, depending on traffic, road conditions and frequency of rest/lunch breaks. We hope to resume staining the deck as soon as he gets here so at least the walking areas will be dry before our Columbus co-trailer trash arrive Friday night.

In the interim, it's lunchtime and we have a tonne o' fresh tomatoes to consume.

Plodding Along

Despite being up somewhat late last night --I was finishing up "The First Elizabeth" by Carolly Erickson, a biography of Elizabeth I. She dies at the end... totally didn't see that coming-- I was up & about fairly early today. There were things to do!

I pushed two loads of laundry through the campground's washer & dryer. Having the facilities here greatly simplified packing: I needed only clothes for a few days rather than, say, ten. As storage space in our trailer is somewhat limited, anything we can do to reduce clutter & bulk has a big impact.

While the laundry was running, I had a shower and made myself as minimally presentable as to not scare off the wildlife, then began catching up on office email from the overnight shift.

My dear employer was scheduled to perform a routine code deployment to the production environments last night. These are seldom pretty events and many times the majority of the fallout and damage isn't apparent until customers begin logging in on Thursday. Since I'm the backup primary on-call, I was expecting to be flooded with frantic debugging requests and calls for assistance, especially in the mid-morning eastern time while the Pacific coast colleagues are in the middle of their early commute to work.

To my surprise, the flood didn't happen as the code deployment was cancelled. I'm not sure if the powers-that-be decided the code wasn't ready for prime-time or if they decided it was too risky to do push new code into production just before everyone vanishes on vacation for Labour Day. In any case, I'm grateful.

Alas, I'm still stymied at the moment on one particular server build. I'd like to use an identical system as a model for my work on this new system but I don't have the passwords for the original. I have to wait for someone to get into the office in California before I can proceed. Hopefully, this minor annoyance of a task will be complete in a couple of hours.

On the good side, my wireless broadband has worked really well. Yeah, I'd like better bandwidth but this is pretty good. My plan has only 250MB/month before surcharges kick in so I've been trying to use it sparingly. Still, three full days of intensive usage has consumed only 70MB thus far so I think I can relax my constraints a little.

kent4str left DC around 10am today so he should be here 4ish, depending on traffic, road conditions and frequency of rest/lunch breaks. We hope to resume staining the deck as soon as he gets here so at least the walking areas will be dry before our Columbus co-trailer trash arrive Friday night.

In the interim, it's lunchtime and we have a tonne o' fresh tomatoes to consume.