On Wed, Feb 25, 2015 at 02:45:26PM -0600, Mark Honomichl wrote: > As a new board member, one of the tasks that I have taken on is to create a > definition of what a System Administrator is, especially in the context of > LOPSA, so I am curious to here what the membership thinks a SysAdmin is. > You can respond on the list, directly to my inbox, or via Reddit ( > http://www.reddit.com/r/LOPSA/comments/2x5i1q/what_is_a_system_administrator/ > ).
A system administrator is someone who deals with one or more systems on behalf of some other entity. Breaking that open: - payment is usual, but irrelevant. There are volunteers. - authority and concomitant responsibility are key. - there is a trivial case for a one-person "organization" - The nature of the systems is not specified, but understood to be at least tangentially related to information technology. Sometimes that involves HVAC, building architecture, or psychology or economics. - There are specialties. There are skills. Some require a few minutes of study, and others need months or years. Although LOPSA has "Professional" in the title, you should remember that the earliest sysadmins were systems programmers, and their predecessors were hardware engineers who were sometimes computer scientists, mathematicians and electrical and mechanical engineers. -dsr- _______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
