>I think that that sounds cool! In essence, I would like to venture forth
>like that. I mean, I don't really want to sit down and program ALL day
>long. Especially if its something I don't want to do... Hmm...seems like
>SysAdm is calling my name.:) Of course, I can still use my skills as a
>programmer and continue to keep them current..
Definitely.
What I love about being a sysadmin rather than a programmer (I've been
both, but always known I wanted to be a sysadmin) is that, with programming,
you get specs, you have coding conventions, you have to comment things, you
are subordinate to the people you're doing things for, etc etc.
But, as a sysadmin, I normally get told by my boss or asked POLITELY by
my users to get something accomplished. I can prioritize it, I can do it the
RIGHT way, not the way some flunky manager has decreed it shall be done,
and I basically have total latitude, as long as it gets done.
The downside is getting up at 3am every morning for a week because,
for example, a Sequent Symmetry has a recurring problem with flaky CPU boards,
or a hard drive is developing bad sectors, or a production system is running
out of space. But personally, I don't see that as a downside, because when I
come in, it's MY system to fix.
My vote is always for being a sysadmin over a programmer. Programmers
are a dime a dozen, sysadmins are the special few who are more than just
programmers. You won't lose your programming skills, trust me.
--
PGP RSA: C992 109C 6D7F 8D91 062E 817E 00D3 287A
"The worst censorship is self-censorship, because fear has no limits."
-- Grady Ward