On Tue, 4 May 2010, Doug Hughes wrote: > I'm sorry (or happy?) but you're wrong. Seems like you're in a bad > position. There are others available.
It seems to me that many positions that require more than just technical work now carry titles other than sysadmin. I think there is a real conflict between sysadmins (who may use the term in a broad sense) and some others (who use it in a narrow sense). I only noticed this fairly recently although I suspect it has been brewing for a while. What is now called a "technical architect" I might call a SAGE Level IV sysadmin. This seems to be part of a trend of specialisation. Quite a lot of people are being employed doing nothing but networking, or nothing but firewall admin, as far as I can see. Compare system administrator and network administrator. As far as I'm concerned any senior sysadmin better be a networking guru but I've found quite a wide variety of opinions on this topic, even among sysadmins. I regard a sysadmin as someone who has both deep and broad experience across a wide variety of disciplines within IT. An experienced sysadmin should be able to design the network, spec out the equipment (deal with vendors, etc) and then build it all if necessary. This has been discussed on SAGE-AU recently. I'm not quite sure what do to about - try to get the message out there and reclaim the term sysadmin or accept that it now has a narrow meaning and find another term. Cheers, Rob -- Email: rob...@timetraveller.org IRC: Solver Web: http://www.practicalsysadmin.com Open Source: The revolution that silently changed the world _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
