It is wonderful to have 8 Perl developers within a single unit. I would be very lucky to be in that atmosphere. I mean it. Instead of focusing for competence, prepare an environment for Perl that all of you can enjoy and grow faster. Have daily/weekly round of discussion as what each person learned. How it can be applied to the project etc.. Consider knowledge as constantly evolving process rather than a set of standards to match. Make the basic processes easier. Make books available. Make the code easily sharable within your unit. Have people look at each other code and make changes. Make use of CPAN, Perlmonks snippets etc. If you still insists on submitting CPAN modules etc.. design in a team, so we can have better modules available.
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.