I first heard of Perl at work. It isn't used a lot, but was used for generating reports that customers could modify to their whims, and I was tasked to make a new one.
I've since used it in most of what I do, even if for prototyping features before modifying the legacy C++ code.
I recently used it to great effect to slam out analyses of 20 megs of log file and provide fast answers to questions while the director and head QA guy were standing at my desk discussing the field problem.
The Python guys around here tend to do more low level things with driver DLL calls and such. I've done more visible things, and quite a few have gone out to other departments and countries.
One thing that might be handy is to package the code up with Cava Packager for example. Just hand off the exe & libs folder and it'll work. They don't need to see the source or rewrite it; make it obvious that the program is already done and in a neat tidy "box".
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:
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||