If your Perl code is so important, you'd better ask to cross train an interested Java dev in Perl so that you aren't a single point of failure for your app.
This arrangement should achieve several positive things:
- provide you with an excellent opportunity to work closely with an experienced Java developer who can offer insights and guidance
- spread the knowledge of Perl in your company, increasing the likelihood that Perl is used when appropriate
- protect your employer from dependence on a single person for a system
- save money by not shipping you off to a Java training class
With your student/mentor person you can have thrilling conversations of the form:
In source file Foo.pm, we are going to do X. In Perl we use the map() and split() functions to do X, blah blah blah. Now, how would you do that in Java?
-
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.
|
