I'd also like to restate your third point:

No matter how bad something is, don't suggest changing it until you've worked with the company for at least a month...maybe more like two, especially if you work remotely.
I'd prefer to say :
Don't suggest improvements without understanding the process. If something seems wrong, try to find out why it is being done how it is, as there may be parts of the situation that you aren't aware of.
The length of time that you've been working there may not have a direct correlation with your actual understanding of the process, and so stating a time period would be inappropriate.

That's a good restatement; better than my original. But I think it needs to have a follow-up point:

Even if you understand the process, you can't productively suggest changes until the client is ready to hear your input. This means you have to "pay your dues" in whatever coin their corporate culture requires--putting in the time, finishing a project, making a contribution, whatever--before you open your mouth.

In reply to Re^2: Professionalism can be bad by Whitehawke
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.