Posted on 11/06/2001 7:11:47 PM PST by Justa
/john
Learn SQL and database systems.
Most major business applications are somehow involved with a database. The various hot languages and applications come and go, but databases live on. 20 years ago there was a big demand for database experts, today there is a demand for database experts, and for as far as anyone can see there will be a demand for database experts.
Different database systems often have their own host language, but almost all of them can be accessed via SQL. Its a default language, and you're expected to know it if you are working with databases.
That IS good advice. I know that an MCSE is not for me (I do Linux and OpenBSD as much as I can). I have found that the ability to do SQL has really paid off in my consulting. I do some database work as part of ZillNet and it is a distinct advantage.
I believe that FR is running on a Linux system/systems. I understand JohnRob is quite certified at this point. Especially after this morning. GRIN!
/john
Companies just don't have the time and money now to retrain employees on Linux. Imo when a stable Linux distro maps closely to '98 and supports legacy DOS programs a lot of companies will switch over. Linux Needs one distro to divert the '98/XP user stream, then *Nixers can quabble over which Linux distro. is 'the best'. Currently, I'm betting on Mandrake will get there first, and I dual boot 8.1 alongside '98 and XPpro.
Studying Linux is like choosing to learn DOS or NT4 -or both. Imo, one should learn both the language and the GUI so he can troubleshoot the GUI. At this time which Linux Distro to follow is still highly debatable. Here's a good rundown on the distros.
Right now I have A+, MCP2000 and Network+ and stil can't get a job locally in the field. Two weeks ago I lost out on a great job to an MCSE because they were migrating from NT4 to 2000. They kept asking if I'd be willing to get the MCSE and I said 'no way, not interested' because of many of the reasons cited in the article. Jeeze, if I'd known they had an MCSE in line I would have told them 'why MCSEs suck'. Famous quotes from MCSEs: "You can't run 2000 Server over Cat3, you'll have to rewire [a 6-building site]" and "the first thing you have to do is install [enter multi-thousand $$$ hardware and MS products here]".
MCSEs are not trained as managers of MS products as much as they are trained as marketers of MS products.
2. Contrary to his point about 4 year degrees, (and I have one) many CS grads I've met don't know beans about computers. In one instance, a Computer Science grad pointed to a memory stick inside a PC I was working on and asked what it was. He then asked me to point out the processor. I spent over a year in a CS program before I realized it would be my senior year before I gained any knowledge of current languages or systems. I tremendous waste of time in my opinion - go for the business degree instead.
3. I've spent four years working in the IT field after having a hobbyist interest for more than ten. My MCSE wasn't worth much in the beginning, and I would have been shocked to have any employer turn me loose on their network without oversight. But I knew enough of the basics to ask the right questions and my skill level has grown with experience. Today, I make a very good living and work doing something I love to do.
4. There are good schools and bad schools. Its up to the student to make a wise choice. There's also been a lot of hype about what a new MCSE will make. Sure, there have been people who got the cert and talked their way into a sixty grand job, but for most 40k is more like it as a starting point. When you consider what a four year degree would cost , versus an eight week training course plus the year of studying and testing it takes the average MCSE student to obtain certification, I'd say its a pretty darn good return on your money. I've invested close to $10,000 in training, and it was the best money I've ever spent.
5. There may be a better way to build a competent work force, but I can't think of one. My Dad went to night school back in the 50's in order to get a better job in the machine shop. Later, his friends came to him and basically said, "If you'll get me a job in the shop I'll go to school." His reply was that they should make the investment in training and then look for the payoff. That's the same thing most new MCSE's do, and as a result the IT industry a pool of trainable, motivated people ready for entry level networking jobs.
Some additional cheery numbers:Hey, no fair!
/john
You either went to a bad school or had way too much fun ;>) I say get an real engineering degree - CE or EE. Then go for a master's in software engineering. So you can call yourself a software engineer and mean it. Then again most EEs write horrific code.
Actually, Linux certification is by professional instruction at an Accredited Center of Education followed by testing through Prometric or VUE.
Hell, I'm willing to take one of those jobs that only Mexicans will do that Americans won't do.
You're right, we wouldn't want UNIX users to have to deal with KDE or GNOME. It just wouldn't be right.
I work Solaris admin in the slave-hold, but use Linux on my free-hold. The Wife is a Novell/Microsloth admin/user. As one who hires and fires, I don't care about certifications. I want to know what you really know about real situations that cost me money. Certifications were supposed to do that. They don't. I'll stick with my sit-'em-down and tell them to type
rm -r /and see how much they flinch. GRIN!
/john
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.