Most IT Workers Don't Have STEM (Science, Tech, Engineering, Math) Degrees
McGruber writes "The Wall Street Journal's Michael Totty shares some stereotype-shattering statistics about IT workers: Most of them don't have college degrees in computer science, technology, engineering or math. About a third come to IT with degrees in business, social sciences or other nontechnical fields, while more than 40% of computer support specialists and a third of computer systems administrators don't have a college degree at all! The analysis is based upon two job categories as defined by the federal Bureau of Labor Statistics: network and computer systems administrator, and computer support specialist."
I prefer education over schooling.
Signature intentionally left blank.
Our best techs don't have degrees. Most of the people who can become skilled techs without having it force-fed down their throat at college can teach themselves, and easily grasp new technology as it becomes available. Most of the people we've hired from college were the "I-can't-do-it-unless-you-show-it-to-me-first" type, which suck to have work for you.
I graduated Grade 12 in the early 80's. Was going to go for a CS degree but put it off for a year while I worked. Then another year went by, and so on.
Back then, the vast bulk of "nerds" loved this stuff as a hobby and could slide into a work role easy enough. Then people started going to school to 'learn teh computerz' as it seemed like an easy way to make cash. Those are the folks who were dumped during the dot-bomb.
Fact is many of the best IT folks I know who also have excellent technical skill were self-taught.
Trolling is a art,
I hold two CompSci degrees (BA, MA) from two reputable universities, and I can tell you this: some of best developers I've ever met have come from non-CompSci fields: geology, physics, and (building) architecture.
The keys to being a good developer are much the same as in any other field: being able to learn, and being able to apply what you've learned, and giving a crap about what you do.
Koans and fables for the software engineer
It isn't...exactly... news, is it, that neither 'computer support specialists' nor 'network and computer systems administrators' are jobs that are particularly close to what a 'STEM' curriculum might teach you. You can't be afraid of computers, and the ability to bodge out some scripts when the occasion demands it is always handy; but it isn't as though you are expected (or even permitted) to break out the CS-fu and build some custom management system, or put your EE skills to work by diagnosing that malfunctioning motherboard properly rather than just shipping it back to the vendor for a replacement...
know what "IT" stands for?
This doesn't surprise me at all. Especially when they mention "computer support specialists and a third of computer systems administrators". These aren't fields that even require a STEM degree in the first place. I'm sure if you just looked at programmers, you'd probably see a much higher percentage with a STEM degree. If I had a stem degree, and was working as a computer support specialist, I'd probably wonder what the purpose of my degree really was. Also, if you have a degree in chemistry, you technically have a STEM degree, but you're probably no more prepared for a career in IT than somebody with a business or fine arts degree
Personally, I've always hated the fact that they even refer to certain jobs as being in the IT sector. It's so large and all encompassing, that it basically fits anybody from a minimum wage support person to a hardware engineer designing cutting edge processors, or people writing financial systems on wall street.
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
For this profile, we mainly focused on two job categories as defined by the federal Bureau of Labor Statistics: network and computer systems administrator, and computer support specialist.
So they looked at the two lowest-paying job categories out of the 8 defined by the Bureau of Labor Statistics, and drew conclusions about the education levels of other six. Hmmm, maybe that's not the best approach...
Have you read my blog lately?
Because in all those professions you can kill people (directly or indirectly) if you screw up because you don't know jack about your profession.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
I got a BSCS degree back in 2003 and I can tell you that it is very much still relevant. You're right, the specific languages, API's, and even architectures have changed dramatically in 10 years, but the fundamentals are all still there. Learning the 2003 vintage of C++ was not so useful (except as an exercise in how to approach programming problems generally), but learning algorithm complexity analysis is timeless. And I'm sure there are more advanced process schedulers in operating systems these days, but they are still being scheduled out there in the background. And so on, and so on.
My great "aha!" moment in my CS degree was when I realized that the specific tool they were teaching in any given class was basically irrelevant - it was just a means to teaching an important concept. Trade schools teach you tools, universities teach you how those tools work. The real value in my BSCS degree was in teaching me how to think about and solve CS problems. That has been invaluable.
...whatever you learned in school is already out of date...
Quite true, but as one of my professors said, "In this course, you will not learn how to code in Turbo Pascal*; you will learn how to learn to code, and then apply that to Turbo Pascal."
A good teacher can make all the difference to impressionable 18-yr-olds.
(*Yes, I am old)
This a perfect example of an article that makes a statement but does not make a conclusion. I guess the conclusion -- perhaps that we should be concerned that our IT professionals don't have scientific or technical degrees -- is implied?
> About a third come to IT with degrees in business, social sciences or other nontechnical fields, while more than 40% of computer support specialists and a third of computer systems administrators don't have a college degree at all!
Panic!
I have an engineering degree, got a job making war toys for a military contractor, needed the computer to do my work, and found that nobody was administrating the computer. In self-defense, I learned how to administer Unix, how to do backups and housecleaning and diagnose problems, all so I could get my primary job done. After several years, when I got burned out on my primary job, (designing stuff for the military is less fun than it sounds) I found that I had learned enough to carry on with systems administration full time.
I strongly suspect that this happened to a lot of people, especially during the rise of the dot coms, and I also suspect that many of them were not originally in engineering. It happens -- people rise to the occasion, and find new career opportunities.
Why is this a problem? Is the admin going to see a countdown someday that says "answer this question that was on the 3rd trimester final in year two of an EE curriculum in 30 seconds or the computer melts into slag"? What you learn in college, other than techniques like ways to attack and solve a problem, are going to be horribly out of date anyway. What you accomplish in the workforce is more up to your commitment and talents, (and training you've sought post-college) than the letters after your name.
Conversely, having letters after your name does not mean you get a free ride (in most companies). You still have to show competency.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
Because, you don't really need one to do the job.. Duhhh!
There is more truth in that statement than many would want to believe. While I was employed at a large government agency that was involved with collecting government taxes from individuals and corporations, instead of hiring programmers, we would take individuals who were familiar with the various tax systems and train them to program. It was our experience that it was easier to train those who were experienced in their field and had an aptitude for development to be programmers than it was to train programmers in all of the intricacies tax laws. I imagine there are a lot of other business and corporate areas where that would be applicable, too.