• crainlee2 (12/5/2008)


    Tony,

    I am starting to see a lot of job requirements listings like this for DBAs, system admins, and software developers.

    We know, and some managers know, that no one has all those skills. People can't live fast enough to acquire them all. And, the technology keeps changing, which makes them a moving target.

    I say "some managers" because I am seeing a trend in the industry toward what I call "career managers". These are almost completely non-technical people who climb the corporate ladder by taking few risks and living on the backs of their subordinates. Their expectations are too high, their knowledge too low, and they are looking for superstars to help keep them successful so they can continue to climb. These types of managers tend to be the ones that place job postings requiring multiple lifetimes worth of experience. They are also the ones that won't hesitate to work their people to death so they can survive and get promoted.

    I've gotten to where I ignore the fact that I don't meet all of a job's posted requirements because no one does.

    I've also noticed that the proliferation of these types of job postings are largely contributing to the phenomenon of "resume spamming". More and more job seekers are sending out resumes for jobs for which they do not meet the posted requirements. Who knows? Sometimes a person gets lucky.

    The sword cuts both ways. If job postings defy rationality, job seekers respond in kind.

    LC

    That's pretty much spot on, so far as I'm concerned. In my previous job, the new IT manager actually scheduled 12 hour days on a project that was way behind thinking that it might make a difference. It did! I didn't think it was possible, but it made things MUCH WORSE! People's already low moral made serious flushing sounds... the "whatever" attitude towards writting code became the mantra... IT people starting finding new jobs in other companies... people fled in droves because it was the "last straw".

    While I agree that the good manager will surround himself with intellegent people and become a "professional delegator", it's important to remember that it's the people around him/her that make that manager successful. It's important to remember that the successful manager will enable his/her people, lead instead of push, and "take some heat" from the upper levels to protect the very people responsible for making any project successful.

    And, if you're a good subordinate, understand that the occasional all night death march is going to happen. Do your best... remember that "When you're going through hell... keep going." If it turns out that all night death marches are the rule instead of the exception, make damned sure that you're not part of the reason that occurs. If you are, then get hot. If you aren't then, you know the choices... in today's economy, choose wisely.

    --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)