Slashdot Mirror

← Back to Stories (view on slashdot.org)

When Should a Consultant Question Decisions?

Posted by Cliff on from the knowing-when-to-grow-a-backbone dept.

bay43270 asks: "Presumably, companies hire consultants because they need technical expertise. At some point (if not on a daily basis) a consultant is asked to do something that isn't in the best interest of the company (and therefore may not be in the best interest of the consultant in the long run). The consultant must ask 'do I just say "yes sir" and go to work, or do I try to explain things? If so, how hard do I push?' When should a good consultant question a decision, and how does the situation differ with contract programmers?"

2 of 436 comments (clear)

  1. You're missing the point by drob · · Score: 0, Flamebait

    Your job is to look pretty and keep you mouth shut. Don't start thinking about "what is good for the client", they don't think about it why should you? Stepping on anybody's toes is going to get your butt kicked out of there sooner so start thinking about what is good for you.

    (did I get the first post??)

  2. Terminal services are not free by Malc · · Score: 0, Flamebait

    Terminal services are not free. You get 90 days to install a terminal services licensing server... which has to talk to the Microsoft Clearinghouse. Perhaps you should look at the Terminal Services Licensing FAQ, it looks like an unnecessary headache to me.