![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I was thinking everything was going awfully fast, why did I think my in-the-office tasks would take 3 hours?
Answer: because they will. Initially, I correctly factored in the sheer pain of sucking the entire dataset from a client site (for as close to perfect replication of the environment as possible in our lab)....
...over a 56k dialup line. Ooof.
It's more done than not-done at this point, having gotten past the worst of the data. Once I have that, I drop it on the desktop, merge in the updated code I wrote, compile, test the whole thing (to make sure the updated code I wrote works). As long as it works, I run a build, drop it in the lab, set up the configuration parameters for the lab environment....
...write an email and go home. Here's hoping it all works that smoothly, I might come in just under three hours at this rate. Put like that it sounds complex, but it isn't, really. It's mostly having the patience to wait for the data to get here.
(I could have shortened it by testing my code while downloading. If I'd remembered to transfer my code to the other machine before dialing into a site whose ip ranges overlap ours, and block out most of the rest of my office. As it is, I'll eat another 10 minutes to an eternity - depending on wehther the code is good or not - for that. Oh well.)
Update: Drat. Code not good. Add at least another 45 minutes, maybe more, it looks like. I've found one of the two problems, if I can just figure out the others, I can get all of this back on track.
Still, not doing too badly. Not giving up my whole Saturday by a long shot, after all.
End result: Four hours instead of three, everything appears to be working and set up, with the database I wanted, even. Yay, getting to go home.
Answer: because they will. Initially, I correctly factored in the sheer pain of sucking the entire dataset from a client site (for as close to perfect replication of the environment as possible in our lab)....
...over a 56k dialup line. Ooof.
It's more done than not-done at this point, having gotten past the worst of the data. Once I have that, I drop it on the desktop, merge in the updated code I wrote, compile, test the whole thing (to make sure the updated code I wrote works). As long as it works, I run a build, drop it in the lab, set up the configuration parameters for the lab environment....
...write an email and go home. Here's hoping it all works that smoothly, I might come in just under three hours at this rate. Put like that it sounds complex, but it isn't, really. It's mostly having the patience to wait for the data to get here.
(I could have shortened it by testing my code while downloading. If I'd remembered to transfer my code to the other machine before dialing into a site whose ip ranges overlap ours, and block out most of the rest of my office. As it is, I'll eat another 10 minutes to an eternity - depending on wehther the code is good or not - for that. Oh well.)
Update: Drat. Code not good. Add at least another 45 minutes, maybe more, it looks like. I've found one of the two problems, if I can just figure out the others, I can get all of this back on track.
Still, not doing too badly. Not giving up my whole Saturday by a long shot, after all.
End result: Four hours instead of three, everything appears to be working and set up, with the database I wanted, even. Yay, getting to go home.
