Still at work.
Mar. 23rd, 2005 06:50 pmIt may be a long night for me, as I'm still at work. I'm debugging a bunch of automated scripts which need to call a bunch of interactive scripts which are used to control our product. The interactive scripts don't really work in a usefull fashion for non-interactive work though, so I've had to tear out their guts and weld them to a scaffold. Its ugly, but it just might work.
The problem is, I've just discovered that the software doesn't run on the test boxes. This has nothing to do with my work (other than I need running software for the scripts to interact with) but there is a training session scheduled for tomorrow morning that will use these very same boxes.
Since I have until tomorrow evening to debug my scripts, but I lose all the test boxes at 9:00 am tomorrow, I'm having to stay late to finish stuff. Now the guy who stayed late to set up the training session is NOT happy, as he was expecting the software to work on these boxes tomorrow. So, we're trying to get things working correctly, so that I can go back to my debuggering and so HE can finish preparing his training stuff.
Grumph.
The problem is, I've just discovered that the software doesn't run on the test boxes. This has nothing to do with my work (other than I need running software for the scripts to interact with) but there is a training session scheduled for tomorrow morning that will use these very same boxes.
Since I have until tomorrow evening to debug my scripts, but I lose all the test boxes at 9:00 am tomorrow, I'm having to stay late to finish stuff. Now the guy who stayed late to set up the training session is NOT happy, as he was expecting the software to work on these boxes tomorrow. So, we're trying to get things working correctly, so that I can go back to my debuggering and so HE can finish preparing his training stuff.
Grumph.
LOL!