Do what I said?

  • I want to know if your manager tells you to do something and you know it is not right, will you do it?

    For example I used to work for manager who insisted to have the job start running at 6:00am, the job was running a DTS package which would read a text file and load the data into the database. The job that created the text file would not run until 8:00am. My DTS package would keep checking if the file existed in the directory every 15 minutes, if it found the file, then starting the load process. I asked the manager why she wanted to start the job at 6:00 am since the the job created the file would not run until 8:00am. She did not give me an answer, but insisted that I set up the schedule to run at 6:00am.

    Would you follow the direction?

  • Sure, run at 6 AM

    First line of code :

    WAITFOR DELAY 02:00:00

     

     .

     

     

    I'd do that if reasoning with the person doesn't work.

  • Either that, or just run it at 6:00 AM to import the file created the previous day at 8:00 AM.

  • While I like the Ninja solution, I'd probably use Lynn's, document it and send my objection in email to the manager when I confirmed it was done. At least that way I'd have a trail if something went wrong.

  • Good point Steve.

     

    But there are advantages when consulting for a small shop .

  • Wasn't it that once said that it's better to ask for forgiveness than to ask for permissions (sometimes).

  • In general I would say follow the directions, but make sure that it is documented.

    Once upon a time I was a DBA and an underwriter of aircraft insurance (my first job out of college).  On this one particular aircraft I refused to underwrite, but got over ruled by my boss.  I refused to do it, and showed him how to log in himself to over rule my underwriting.  A week later the aircraft crashed.... Since my name was all over the underwriting notes, I got chewed out for underwriting it, until I pointed out that I had in fact declined on it and that the boss had done the final underwriting.

    Documentation is key

    In Loner's case I would say that is pretty assinine to request the job to start at 6 if the file would not be done until sometime after 8.  Why not fire of the job she wanted at 6 automaticaly from the job at 8 when it was done?  I do that here on a lot of batch jobs that creates files out of non-SQL systems that needs to be imported.

  • Not sure it's better, but it is easier

    Definitely document things. Sometimes there's a reason you're not aware of and sometimes someone is just being an idiot and it's possible they're setting you up for failure. Do what they said, maybe request it in writing if you know it's wrong and then document what happens.

  • Thanks. After all these years I think I still do not know how to play the politics. That is why I always get in trouble.

    It does not matter if you are a good developer, it matters that you know how to play game with your upper management.

  • Not if you sink the boat in the process.  There may be a reason the manager wants things done a certain way (it's usually political).  Of course, the manager just might be a dirt-bag that doesn't know what (s)he is doing but if you disobey your manager's wishes, you better be right... damned right... and with lot's of backing because even if you're right, it could still be taken as insubordination which is one of those funny things they can fire you for in a lot of states.

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

  • quoteNot if you sink the boat in the process.

    No Chance. I'd have thrown my boss out of the boat already and be hitting them with the oar

    In cases like this, I'd refuse, document it and let relevent people know to cover my a$$, eg boss' boss or my boss if it is my boss' boss

     

    Far away is close at hand in the images of elsewhere.
    Anon.

  • it really depends on your boss. will he open to listen to you & welcome other ideas? i'd usually started with "this is where we are and what would be your opinion, what are your thoughts on...", so it'll come out as his decision, after all he's responsible for everything, but ultimately the right practices are being used. is it what you are after?

  • It seems I always encounter this kind of manager. I have a new manager in June, he is stubborn and arrogant, do it my way or no way. He wanted me to change a procedure and he wanted to do it certain and he said it was easy, it probably would take me an hour to do it. Since he is new and does not know the system so I explain to him it is not as simple as he thinks. He emailed me with bold letter said 'WHAT IS YOUR PROBLEM, WHY CAN'T YOU DO IT'. I considered it was very rude especially it was written from a manager. He was a developer and got into manager position because the company could not find one at that time. Here is another example that not all developers can be good managers !!!!!

  • LOL... I just knew I liked you for more than the code you write   I'm getting soft in my old age and forgot just how effective and satisfying splintering a perfectly good oar over the head of an ignorant PIA can actually be

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

  • Loner,

    In the situation where your boss says something is easy and you don't think it is, try sitting down with him and asking about it.  Tell him something like, "Okay, maybe I am over-complicating the issue.  Please tell me what you see as the resolution since I obvious can't see it."

    He might actually have spotted something you haven't.  And if it is a case of him missing an obvious problem, when he gives you his solution tell him, "Okay, I can do that, but this is what is going to happen when I do... Are you sure you want me to do it?"

    If he continues to say yes, send him an email documenting the conversation with a premise line of "I just want to verify I understood our meeting correctly.  If you could look at the below summary and conclusion and let me know that I am in fact understanding what you need me to do, I would greatly appreciate it."

    Then you will have, maybe, smoothed the way of communication with your boss as well as done some CYA.  If you're really paranoid, make sure, of course, to save the email and its reply in a couple of different locations (PC at work, hard copy, and a copy at home). 

    Believe it or not, we all have these conversations with our bosses.  I had one the other day, though I was the one telling him the fix was much more simple than he thought. @=)  It's just a matter of presentation. 

    Here's an odd thought.  If your company offers a phone manners course or a customer service course to their sales / CS people, ask if you can sit in.  Yes, the courses can be boring, but they tend to go over how to handle irate customers.  Technically speaking, your boss is an irate customer, so the course might teach you some methods for actually handling him.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

Viewing 15 posts - 1 through 15 (of 23 total)

You must be logged in to reply to this topic. Login to reply