Slashdot Mirror
A Title To Replace "Systems Administrator"?
sjanich writes "A discussion has begun at SAGE on an updated title to replace "Systems Administrator". I figure more sysadmins are reading Slashdot than are reading SAGEwire. Rob Kolstad of SAGE wrote: 'What in the world do we call the collective group of those people who make computers work properly? I'm not talking about users, and I'm not talking about software developers. I am thinking of: system administrators, LAN administrators, network administrators (both kinds!), security administrators, e-mail administrators, desktop support groups, database administrators, and all the other kinds of support that keep the IT function of an institution running -- what is this huge group called?' My favorite options are "Computer Infrastructure Practitioner" or "Computer Infrastructure Specialist". The original discussion can be found here at SAGEwire."
OMFG what a lame ass topic, sorry, but wtf is wrong with sysadmin?
"Guy with a Small Penis"
rolls right off the tongue!
I'd insist on a job title of "Lord Uber-Geek". Rolls right off the tongue!
Or perhaps Hooche Moma (however you spell that
Obnoxious know-nothing do-dothing assholes. Most Sysadmins would rather explain why something cannot possibly be done rather than just doing it. In the time they complain most programmers usually just fix it themselves.
So to recap: Sysadmins - feed those CDs into the drives like the good monkeys you are. Yeah, that's right - you're a bunch of useless monkeys.
but Lord and Master works just fine with me...
engineer my ass.
digital janitor.
These are the people who figure I have to use Microsoft products on my desktop, and am not even allowed to do such security-threatening things as change my font size, create a directory, or heaven forbid, install Mozilla (because I'm so sick of dealing with IE I want to punch someone).
So I hate my work environment, I work at about 1/2 speed, because I have to use the crappy point-and-click interface to everything, and the first good offer that comes along...see ya!
If there are any sys admins actually listening to this, am I unlucky, or is it really the consensus of those in your profession that locking down a software developer's workstation so tight that he gets to breathe air only when you provide it is helpful in some way?
Because my belief is that if a malicious employee wants to cause mischief on a machine where he has physical access, it's a piece of cake. But creating an efficient, user-friendly workstation is a completely different matter, and requires access.
Not to hard to tell how frustrated I am over this, I hope.
Any pompous sysadmin who asks me for a title upgrade is going to be hearing a few weeks down the road how the receptionist is doing a great job at covering his duties since he was "downsized." With 10 days of moderate OJT, any Jack or Jill off the street can do what most sysadmins do, and without the holier-than-thou attitude toward their customers (the users). They might not know all the fine nuances of technology we don't use ("grand" open source crap that a "professional" sysadmin would pine for), but they'll know how to do their job and serve the bottom line, leaving strategic decisions to managers who have an actual clue about the business world.
DICKHEAD