Well, perhaps the only recourse you have is write a clear document why it's not a good idea to drop Perl. Start with organizing - find out who else thinks it's a bad idea to drop Perl - a counter document carries more weight if it's signed by a multitude of people. Make sure the document focusses on why it's bad for the company to drop Perl. Make sure you can back up your argument with facts - just saying that it takes the same amount of resources (== money!) to develop an equivalent program in Perl than a program in Java doesn't say much. If you have figures (which means, you got to do some research) to back up your claims, your arguments will be much stronger. Remember that your document has to be better than the one of the Java guy - he has already won a major battle.
Abigail
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- 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
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
