This item text has been erased.

14 responses total.

Ooh... I probably wouldn't have the chutzpah to do it... but I'd drop
hints, maybe show the 'bad code' (don't you hate it when people don't
comment!) and make sure they know what this person is like.  I wouldn't
be able to tell them directly though.

I'd probably point it out.  However, my boss seems to be better at figuring
out that people don't know what they're doing than I am.

If this individual writes code so rude viruses run screaming, yes, I'd ttell.

YES! Ithink someone who does a job badly shouldn't do it at all.

I tend to let the administration do their job and I do mine.
Not out of laziness but out of respect.  I've never had a 
supervisor who wasn't astute enough to be able to see how
things were going.

This response has been erased.

        Of course I would, unless the chap had serious connections.  No point
in banging your head against a brick wall that fights back.

YES!

        I would probably put a lot of time and thought into that one. On one
hand, everybody would have to put up with it if they did come back, but you
might lose your job for putting your rear on the line to administration.

I guess to me, it would depend on my 'loyalty' to the supervisor /company in
question.  I have worked for people that I felt deserved to know, and that
they valued any 'help' along the way.  I have also worked for people who would
feel 'threatened' by such a statement, coming from someone below them.

Does writing bad conde infer incompetence? or sheer meanness?  If  the person
wrote bad code because they were incapable of writing good code, then it's
possible they've learned how...If the person did it out of boredom or spite,
that personality is unlikely to change.  I'm wondering why management doesn't
already know, since so much time was spent correcting the situation.  So,
my answer (and yes I do have one here somewhere...) is "no, don't tell"
if the person was clueless and give them a chance to show they've learned.
But definitely let management in on it if the person is deliberately
bringing the company down.

I suppose that if you value your job enough, one wouldn't tell the company
about th mistake.

Give him a chance, see if he has improved. Let us accept one thing, all of
us soemtime or the other have written bad code ( how many times haven't we
felt that the code we had written last week or even yesterday was junk). The
issue is , has he leart from his mistakes. if he hasn't then it requires a
stronger action. Ignorance can be forgiven but not stupidity. Tell the
supervisor ( if he doesn't already know) he has hired the wrong guy.

Without fail, it seems that invariably in any organization, management seems to
be the department most prone to incopmpetence.  Unfortunately, if I am not in
management, it is not my job to overly criticize or point out flaws in execut
decisions unless otherwise informed by my job description.
  Therefor, I do my job, and if that curtails cleaning up someone else's 
mistakes, I do it and grumble to myself, but it's what I'm being paid
for; if I don't like it, I quit.  If my job does not include this, I
voice my complaint, and otherwise refuse to do that work.  
  Ultimately, bad hiring practices reflect in poor work output, and this
in turn reflects upon the hirer.  If this person's superior is doing their
job correctly, things will be rectified albeit, not necessarily in a 
timely fashionn.

Response not possible - You must register and login before posting.

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss