• I have to disagree a bit with the aspect of not saying anything if someone doesn't meet expectations. There's no doubt that not everyone on a Team is going to be equal. I very much agree with the intelligent manager that will find the niche that a "misfit" can really excel at and become a productive and contributing member of the Team.

    But there are some real bucket-for-brains managers out there that simply don't pay attention or that simply can't handle conflicts of any kind. You all know the type I'm talking about. I've worked for a couple of managers that have allowed slackers, posers, fakers, arrogant sots, those that practice malicious compliance with rules and standards, whiners, and a few other ugly personality types to continue at the company and, yeah, you know those types, as well. These types of people can very quickly destroy a team and if the manager isn't doing anything about it, then you're doing the company a diservice by not taking it up the chain. And, before you do that, you need to make damned sure of two things... 1) you're right and 2) your not a problem yourself. And, yeah... there's a right way and a wrong way to do this but keeping your mouth shut might not be the right thing to do either.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)