Personally, I'd prefer that he came to me, told me the
sequence of events and the conclusion about the memory
footprint.
Concur.
You don't need to be a dick about it, just mention that
you were interested in the guy's script, that it seemed to
be taking a while, and maybe you could get together and see
about making it a bit faster? If you play up your interest
in the other guy's script, he shouldn't be terribly insulted
that you're suggesting an improvement (especially if, as it
sounds, it was a quick hack to fix a common problem in as
little time as possible).
On the other hand, if you're more interested in keeping
out of trouble with your boss (not a criticism; I think
we've all had jobs where we're mostly interested in keeping
our heads down and out of trouble, and waiting for daylight
to get the fsck out of there), you might be better off
talking to your supervisor, mentioning that you were playing
with the code before he came by, and suggesting that you and
the other support guy collaborate on a re-write (helps if
you have an idea of what kinds of changes to make before
hand, to limit the "don't change that code, it's not worth
the time" factor).
--
F
o
x
t
r
o
t
U
n
i
f
o
r
m
Found a typo in this node? /msg me
The hell with paco, vote for Erudil!
| [reply] |