"So you see, I hate perl. I hate software developers. I really wish you would all grow up and learn how to be the professionals we pay for."
All I see is hatred. Perhaps having an open mind along with a willingness to discuss with your teams and management on how the personnel issues could be rectified may better your outlook.
You don't have a Perl or systems problem, you have a personnel, policy/prodecure and personal attitude problem.
Embrace the difficulties, document the issues, and bring them to light. At least that's what I did in my two decades as a global network engineer and systems engineer/administrator, all the while being a software developer.
Discuss with the development manager and team leads the ideas you have to streamline processes instead of just grunting about them privately on an Internet Perl forum. Make an attempt to fix things internally. Be the quality systems admin that you're being paid to be.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.