It is my opinion that you can't be a great SA and a great coder.
Why not? Is there some great piece of IT folklore out there that the skills for one preclude the other? In my opinion, this is like the other great myth of the corporate world - that you can't be good at IT and a good manager. I have encountered several exceptions to this, and I recommend looking for and supporting any boss who is skilled in both areas. You need a manager like this to help you fight any battles over infrastructure.

Coming back to sysadmins. I have been a Unix and VMS sysadmin, I have also been a developer, support person, business analyst and tester. Perhaps it is because I have been a sysadmin that I can appreciate the role, and I tend to make my sysadmin colleagues' lives easier for them (I am currently assigned as a developer and application support person).

Having experience as a sysadmin gives you insight into a number of programming and design issues, for example:

In my opinion, someone who has not been on the sharp end of these issues as a sysadmin will fail to grasp the consequences of what they are programming, and will write code that fails one or more of these criteria.

My $0.02

--rW

In reply to Re: Beginning Perl for system admins by rinceWind
in thread Beginning Perl for system admins by jjohnson

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.