comment on

This may be common sense and something everyone here's already thought of, but it could help your situation if you can find some "good" practices, code, etc. to comment on as well as the bad and/or ugly.

When I was hired for my current position, I was brought in to be the new "Web Guy," as the people currently handling the organization's website had no real web design experience. A lot of what I found waiting for me needed serious improvement, mostly due to inexperience. About a week in, I was asked what I thought of the site, and I was able to truthfully point out several things that had been done right and several stylistic pitfalls that had been avoided.

I believe this gave me a bit more credibility with the people who had been handling the site before me (one of whom is my supervisor), and combined with constructive criticism of other areas of the site, stopped short of ye olde brown nose. ;)

-rattus, this'd be my $0.02 if rats carried pocket change

In reply to Re: OT: Job Advice by rattusillegitimus
in thread OT: Job Advice by abaxaba

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks