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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||