One of the problems that you're describing is the fact that the programmers B&M when you install a new perl version over the old one, and you wonder why they aren't using the latest and greatest in features and avoiding those that have gone by the wayside.

This attitude makes the sysadmin look like a jerk.

A sysadmin must be able to communicate with the users of a system, not only to inform them of upgrades and changes, but to also listen to users who need certain features. Just because you know the root password does not allow you to act like you are their manager.

At nearly every site I've been at with shared machines, the sysadmins would announce major changes to software at least 2 weeks in advance if not sooner (with several reminders in between). If the software was a minor change, it would usually be installed right over the existing one, while major changes would involve shuffling directories and scripts from the sysadmin end to make sure that both the old and new versions were usable. In cases where old versions had to be dropped (as supposed any more than 2 major revisions of software is a pain), the users were given several months of time to prepare, and in rare cases, the old version was installed on a specific low-use machine for those users that could not abandon it.

In nearly all cases, there was also a way to access the cutting-edge versions of programs as well, but you had to ask the right people. But as with the old versions as well as these versions, the sysadmin flatly stated that no tech support will be available beyond standard problems.

And to the best of my knowledge, the sysadmins worst complaints were that people didn't know what pine's "Reply to All?" meant, and why it was on by default (in reality it wasn't, but users always hit 'y' anyway for this).

In addition, this doesn't just apply to perl. C, C++, Java, and major applications all have similar possible problems with new features and outdated functions. Perl might be a faster moving target than those, but the same ideas still apply: the sysadmin must be in communication with their users at all times in order to do an effective job, instead of acting like a god that does magical things when they feel like it.

Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain

In reply to Re: Why I hate Perl (discussion) by Masem
in thread Why I hate Perl (discussion) by deprecated

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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, details, 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, summary, 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.