Small Mosaic


Categories:

books
career
codinghorrors
comics
events
geekstuff
justdont
languages
languages/bash
linkshot
magazines
meta
misctech
movies
nottech
operatingsystems
operatingsystems/linux
operatingsystems/linux/debian
operatingsystems/solaris
paranoidadmin
perl
python
ruby
security
security/apache
security/tools
serversmells
sites
specifications
sysadmin
tools
tools/commandline
tools/firefox
tools/gui
tools/network
tools/online
tools/online/greasemonkey
unixdaemon

Archives:

October 20085
September 20084
August 200812
July 20089
April 20084
March 20081
February 20081
January 200815
August 20072
June 20079
May 20076
April 20078
March 200731
February 20073
January 200721
December 20061
November 20064
October 20066
September 200632
August 200617
July 200614
June 20069
May 200613
March 200611
February 200616
January 200611
December 20051
November 20056
October 200519
September 200525
August 200516
July 200516
June 200513
May 20052
April 200519
March 200531
February 200520
January 200531
December 200421
November 200430
October 200432
September 200418
August 20047
July 200414
June 20045

Tue, 02 Nov 2004

The Nature of the Beast: Sysadmins
While I'm in this navel gazing mood (which shouldn't last very long) I thought I'd say a little bit about the oddness of being a system admin in a corporate environment; it might be the same in academia but I've never done that.

Firstly you have the contradictions, in most companies, and heavily so in a small team/company, you are supposed to be open and approachable. But you also have to manage your time, their requests and the sanctity of the live environment. Saying 'no' a lot doesn't make you very popular. It is also this last one that causes the most grief, ensuring the service is running correctly becomes your responsibility. You have to become seriously paranoid, pessimistic and suspicious about any changes that need to be made while also understanding that the system is there for a reason; to be used.

I've mostly had this discussion with management and developers, the quality assurance team normally provide some support, once you've had a failure and 'requested' that whoever wants the change added is present for as long as you are things typically get better. For a while anyway.

Something that also deserves a mention is the sheer agony of joining a new company where not everything is perfect, or as we call it, all of them! You have to be prepared for everything to go wrong. Inconsistent naming, multiple copies of config files (and of course you need to edit the one in the non-standard location), lack of documentation and being expected to work at the same speed as the people that have built the system all add up and combine with the paranoia, pessimism and defensive instinct.

Being a good sysadmin and a well balanced person seem to be mutually exclusive goals. No wonder there are so many social groups for geeks, not only do we need to escape from the server room but we need to socialise with 'our own kind' ;)

Like this post? - Digg Me! | Add to del.icio.us! | reddit this!

Posted: 2004/11/02 21:13 | /career | Permanent link to this entry | This entry + same date


books career codinghorrors events geekstuff justdont languages/bash linkshot magazines meta misctech movies nottech operatingsystems/linux operatingsystems/linux/debian operatingsystems/solaris perl python ruby security security/apache security/tools serversmells sites specifications sysadmin tools/commandline tools/firefox tools/gui tools/network tools/online tools/online/greasemonkey unixdaemon

Copyright © 2000-2005 Dean Wilson XML feed logo