Comment some suggestions (Score 2, Informative) 903
With a "useless" degree in journalism, I got a crummy job doing inbound sales at a large call center. While reciting my mindless sales scripts, I read every computer book I could get my hands on and "explored" the internal network. When I finally got fired (couldn't take it anymore), I made a resume that consisted of a list of the books I had read, and that got me a job as a computer operator. Two years of that and then I got my current job, administering badass IRIX systems at a satelite ground station.
Too old?
Well how long are you going to live? Most people have to work after age 65. Many retirees end up going back to work out of bordeom, etc. Considering the amount of years you will have to work, wouldn't you rather spend the time doing what you love?
I could give you numerous examples of people who came to their calling later in life. People who became doctors, composers, etc., but listing them would bloat this response. I think when people are too old, that means they don't feel like starting over, accepting lower pay or subordinant status, etc., they want to play it safe.
Value of degree
A degree in CS is good to have, but I have been appalled by how many CS grads I meet who know almost nothing about Unix, not even a historical overview. Still, I think a degree is largely what you make of it, so a person who loves the subject will probably be better than someone who coasts through just because CS is a degree that will get them a job. My boss has a history degree, my predecessor has a chemistry degree, most of the other computer operators from my first tech job had no degree at all and many have become Unix or NT admins.
Passion for what you do
This is, I think, my edge over many of my peers. I have what is to me almost a dream job, but many of my peers got into computers because it was a good job, others just aren't working in the right area of the field, they don't love what they do. Look how many of these comments express that sentiment. Passion for what you do is hard to put on a resume, but it definitely counts as far as real world results are concerned.
Value of certification
Some here have downplayed the value of certification, saying that what really counts is being able to work in the real world. That's technically true, but for someone with no CS degree and little professional experience, a certification can lend credibility to the skills you claim.
There are tons of MCSE's out there, and you can find training courses for the program all over the place, but there is a real lack of good training for Unix, so a Unix certification may be worth more than some other certitifcations. Comptia now has a Linux+ certification, and there are a few other certs out there, all of which should be atainable for someone willing to work with a few study guides. I wouldn't suggest getting more than a one or two, though.
Adapt existing skills
Figure out how to use your non-tech skills. With a journalism degree, I am able to write and communicate better than most of my peers. These types of skills are helpful in getting your job and succeeding in it(people often think admins don't do anything because they don't see most of the work, and don't understand what they do see. I made the mistake of concentrating ONLY on technical competence for the first years of my career: management failed to recognize my capabilities because I didn't communicate them.
Get some experience
You could start with a lower pay, junior level position. There are also some creative ways to get experience. Become a computer consultant (this might become profitable, but certainly you can get some experience, especially if you are cheap). Teach some beginner classes in Linux (parhaps for free at a local library). Maybe even contact a local training center about teaching some courses(especially if you have a certification). Write an article or book. And finally, host your own Unix based website, effectively making yourself a Unix Admin (on a small scale). Add as many administrative needs to the site as you can (database, user accounts, etc.) so as to get more types of admin experience. Or do the ulimate and create (or help create) something that lots of people will use, like a useful utility.
Finally, make friends with other Unix lovers.
Too old?
Well how long are you going to live? Most people have to work after age 65. Many retirees end up going back to work out of bordeom, etc. Considering the amount of years you will have to work, wouldn't you rather spend the time doing what you love?
I could give you numerous examples of people who came to their calling later in life. People who became doctors, composers, etc., but listing them would bloat this response. I think when people are too old, that means they don't feel like starting over, accepting lower pay or subordinant status, etc., they want to play it safe.
Value of degree
A degree in CS is good to have, but I have been appalled by how many CS grads I meet who know almost nothing about Unix, not even a historical overview. Still, I think a degree is largely what you make of it, so a person who loves the subject will probably be better than someone who coasts through just because CS is a degree that will get them a job. My boss has a history degree, my predecessor has a chemistry degree, most of the other computer operators from my first tech job had no degree at all and many have become Unix or NT admins.
Passion for what you do
This is, I think, my edge over many of my peers. I have what is to me almost a dream job, but many of my peers got into computers because it was a good job, others just aren't working in the right area of the field, they don't love what they do. Look how many of these comments express that sentiment. Passion for what you do is hard to put on a resume, but it definitely counts as far as real world results are concerned.
Value of certification
Some here have downplayed the value of certification, saying that what really counts is being able to work in the real world. That's technically true, but for someone with no CS degree and little professional experience, a certification can lend credibility to the skills you claim.
There are tons of MCSE's out there, and you can find training courses for the program all over the place, but there is a real lack of good training for Unix, so a Unix certification may be worth more than some other certitifcations. Comptia now has a Linux+ certification, and there are a few other certs out there, all of which should be atainable for someone willing to work with a few study guides. I wouldn't suggest getting more than a one or two, though.
Adapt existing skills
Figure out how to use your non-tech skills. With a journalism degree, I am able to write and communicate better than most of my peers. These types of skills are helpful in getting your job and succeeding in it(people often think admins don't do anything because they don't see most of the work, and don't understand what they do see. I made the mistake of concentrating ONLY on technical competence for the first years of my career: management failed to recognize my capabilities because I didn't communicate them.
Get some experience
You could start with a lower pay, junior level position. There are also some creative ways to get experience. Become a computer consultant (this might become profitable, but certainly you can get some experience, especially if you are cheap). Teach some beginner classes in Linux (parhaps for free at a local library). Maybe even contact a local training center about teaching some courses(especially if you have a certification). Write an article or book. And finally, host your own Unix based website, effectively making yourself a Unix Admin (on a small scale). Add as many administrative needs to the site as you can (database, user accounts, etc.) so as to get more types of admin experience. Or do the ulimate and create (or help create) something that lots of people will use, like a useful utility.
Finally, make friends with other Unix lovers.
