Work and Week
This week's been a blur with work. Monday wasn't too bad. Tuesday through Thursday were almost full-day training sessions on new circulation software. For the most part, it actually went well. We got most of the usage covered. Most of it made sense to the right people. And most everything worked, even if the data set we were using is far from final.
Mostly.
Wednesday morning, after having set everything up downstairs, I was told we'd have to move because of a "small electrical fire." Uhh... So scrambling to relocate all the equipment set us back a little. It turns out the ballast in one of the fluorescent lights had shorted or something, melting plastic and making a bit of a mess as well as a very bad smell. I'm not sure if there was actually flame involved. This was frustrating, but what can you do?
There was also one piece of the admin tool we were looking at that was responding painfully slowly for reasons we have yet to figure out. And another where information had to be entered in the precisely correct (but not obviously clear) order to avoid putting the admin tool in a loop that requires closing it and starting over - not a great selling point.
There are also still a few points where the vendor personnel and our people aren't quite communicating with 100% clarity that are slowing us down in the conversion process.
But while I've been working late (and may edge into overtime today even if I leave early) for a few days and my brain starts to want to glaze over after the first 5 hour or so of sitting focused on something like this, it generally felt productive. And that's good.
Of course, it would be better if we weren't also having connection problems with our remotely-hosted editorial system this week.
Mostly.
Wednesday morning, after having set everything up downstairs, I was told we'd have to move because of a "small electrical fire." Uhh... So scrambling to relocate all the equipment set us back a little. It turns out the ballast in one of the fluorescent lights had shorted or something, melting plastic and making a bit of a mess as well as a very bad smell. I'm not sure if there was actually flame involved. This was frustrating, but what can you do?
There was also one piece of the admin tool we were looking at that was responding painfully slowly for reasons we have yet to figure out. And another where information had to be entered in the precisely correct (but not obviously clear) order to avoid putting the admin tool in a loop that requires closing it and starting over - not a great selling point.
There are also still a few points where the vendor personnel and our people aren't quite communicating with 100% clarity that are slowing us down in the conversion process.
But while I've been working late (and may edge into overtime today even if I leave early) for a few days and my brain starts to want to glaze over after the first 5 hour or so of sitting focused on something like this, it generally felt productive. And that's good.
Of course, it would be better if we weren't also having connection problems with our remotely-hosted editorial system this week.
Comments
Post a Comment