If you feel those aspects deserve greater attention from management, draw up a comprehensive map of how the various components fit together, showing the gaps that must be filled in. At that point you can talk about how important Perl is to the project.
Frankly, it might be better to just keep quiet about Perl. If management becomes aware that massive amounts of coding is being used, there's the risk that some PHB will say, "Hmm... We should be doing that in Java."
Sometimes, the only thing worse than a manager who doesn't know what you do is one who does.
Wally Hartshorn
-
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.
|