my work rant..

[imported_vr6]

I have given one executable two two dlls. One dll is 3years old, and the code for that dll was lost. I have another dll, newer one which i do have code for.

Theres suppose to be a bug in the new dll that the old dll fixed, but since we don't have the code, we don't know what it is.

so after running about 40 different scenarios of input and processing them with the seperatly with the two dlls, the results were pretty much identical.

i am frustrated beyond belief. I guess this is the case where they give the interns the crappy work that no one else wants to do:|

 

[Hankerton]

Yeah, screw em. Tell em to find their own dlls.

 

[FoBoT]

i like dill pickles


but not keeping old source code is an easy execuse to not update old progs

 

[imported_vr6]

Originally posted by: Hankerton
Yeah, screw em. Tell em to find their own dlls.

i wish i could just tell them off. all this pent up frustration can only lead to one thing..

 

[imported_vr6]

Originally posted by: FoBoT
i like dill pickles


but not keeping old source code is an easy execuse to not update old progs

they just told me that it was "lost"

 

[Hankerton]

Originally posted by: vr6

Originally posted by: Hankerton
Yeah, screw em. Tell em to find their own dlls.

i wish i could just tell them off. all this pent up frustration can only lead to one thing..

chronic masterbation?

 

[Gibson486]

i am in the same boat. I am on a project where they told me to rewrite these 3 dll's. They work now, but it crashes in another DLL. They told me to just find a work around for it. Easier said than done.....

 

[imported_vr6]

at least your are doing something new, i run the same application 40 times, alternating between two different DLLs, take the result from each run, and comparing it to the result created using the DLL.

gets old really fast.