Definitely. Know your stuff, show up on time, do quality work and get along with everyone else on the project.

Well .. maybe. You have to get along with the people on the project. I would prefer to remain my own person, however.

You don't have to overtly tell the client that they're wasting resources doing it the wtrong way .. but you can educate them about alternatives that you know about that could offer them improvements.

Don't press to begin with .. if you have time to give them a very short demo, do that. If you're a consultant, one of the things that they're hiring you for is your expertise, your knowledge of the industry. If you can save them time and/or money, it's practically your duty to tell them about it.

If they choose not to take you up on your suggestion, that's their privilege .. and they may know thigns about the company which may not permit your suggestion.

Well .. maybe. This is like the second point -- you do have to get along with them.

Absolutely. That person deserves to be earning respect and big bucks.

Great post. Very interesting stuff. I love to hear stories from 'the front'.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds


In reply to Re: Professionalism can be bad by talexb
in thread Professionalism can be bad by Whitehawke

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.