![]() |
hgfhgf
.
|
Re: Changing career paths...
Quote:
If you were switching to say sanitation engineer that would be a different story. :D |
Re: Re: Changing career paths...
.
|
Hey the direction change is no problem, but the pay cut is bad news. It often takes many years to make that up. Consider that aspect very carefully.
|
How can you be an SMS admin and not have any hands on experience? Is it just being used for patch managment?
|
Working with Linux/UNIX/Networking, in other words, non-windows, is the TRUE Enterprise environment. Throw in some SAN/NAS experience and you can pretty much write your own ticket. It may take you a while to catch up in pay, depending on what you are at now, but you will be much more marketable. I'd suggest taking a couple of Red Hat courses and getting the RHCE cert. No matter how bad folks hate Red Hat, or prefer other Linux distros, it is pretty much the defacto standard. You can run RHL on a cheapo computer for practice. Get a cheap Cisco router and switch off ebay and start dorking with that as well and get a couple of systems talking on your LAN at home. I say do it. I sure would not want to be a Windoze admin with Vista finally arrives... :)
I'll also add that I will almost always hire a Jr. person with a good personality and positive attitude over a whizkid who would rather sit in a closet. Tech skills can be acquired, personalities and common sense cannot....at least when we're this old. |
I agree with bb80sc. Good post, good advice.
|
.
|
Do you think you have a shot at the Jr position?
I AM that dedicated network engineer you talk about but I maintain a subset of skills in the linux environment so that if need be I COULD change to a Linux sys admin role. It's always made me more valuable. My suggestion would be to lay low in your current job and start hanging out with the network engineers. Networks are much easier that systems because they are typically simpler (at least they used to be). But these days with load balancing, content switching, redundancy and all the things "required" to operate and maintain status it's not as easy or "best effort" as the internet used to be. In that three months you have off maybe consider studying up on what a "Network" is. I'm sure you have quite a bit of the pieces of what it is but you'd be surprised at how many Sysadmins know ip addresses and cables but don't really understand networks. My suggestion is to get a CCNA book and start reading. The more you already know the more you'll understand it, the more you don't the better you will after reading it. It's a win/win situation. A Sysadmin with network know-how is valuable, a Network engineer with System know how is 10 times more valuable in my eyes. I can't tell you how many times I have been able to say "it isn't the network; because it *IS* this." OR even been able to say "It *IS* the network....dammit." Stay where you are making the salary and hang out with the network engineers. |
.
|
[.
|
Re: Re: Changing career paths...
Quote:
|
All times are GMT -8. The time now is 11:39 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
Search Engine Optimization by vBSEO 3.6.0
Copyright 2025 Pelican Parts, LLC - Posts may be archived for display on the Pelican Parts Website