First - Thank you for writing this document. Taking the time to enlighten others is highly commendable.
For those who flamed -
It's obvious that you're passionate about perl, otherwise you wouldn't bother answering questions here. This person put forth something to help others perform and understand. You have the brainpower, be a productive source of information for this writer.
Was there anything technically wrong or misleading in the document? What could be done to improve the clarity? Is it focused and phrased for the intended audience? As a skilled resource, these are the sort of things you should be considering and commenting on.
Few people realize how many non-technical people are forced into technical roles at their work. I've met more admins who've had root access to production servers than I'd care to admit. They don't get any technical training, don't have any previous background, yet their jobs require them to do "administrative functions" like create accounts, schedule batch runs, you name it.
If people don't learn perl here, they will learn it elsewhere, and then generate more useless, convoluted scripts all over the place for the next engineer to forklift rewrite.
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||