I'm working on a project to improve a process in a recently finished application. The improvement is necessary because the process I'm improving takes a hella long time, much longer than is reasonable. Some unfortunate SQL table design (not mine) and a foreign key constraint are to blame.
I have a nice project plan written, good testing steps planned. So today I'm getting ready to start the project and I think to myself, "Self, before we get started improving this application, let's do us a baseline to measure the aforementioned proposed improvement against." So I went ahead and kicked off that process at around 1:30 pm. Now I'm kicking myself because the ill-behaved process is still running and it's been more than 2 hours. My consolation is that after my improvement the process will take less than 5 minutes.
I really wanted to start doing the project work today, but can't do anything until this process finishes (or I kill it, which is looking more and more attractive). I guess if it's still running tomorrow, I can kill it. Do you think "Takes way too long" is good enough for a baseline measurement? Maybe I will kill it now.
Posted by buggy at July 1, 2003 03:53 PM