Slashdot Mirror
Mixed Signs On the State of IT Education
snydeq writes "Advice Line's Bob Lewis comments on the mixed state of IT education in the US, which sees some students graduating with computer-related degrees despite never having written a line of code. And while some institutions are emphasizing the value of teamwork in their curricula, an approach that fosters specialization in lieu of uniform standards, others are simply advertising their 'success rates' in graduating students. 'Education is a marketplace, and if you have the money and want to buy, you can find someone willing to sell,' Lewis writes. In other words, 'If you want a degree that indicates you know something about computers without having to actually know very much about computers, you can get one.'"
When I have people applying for roles here, I have found some rather funny perceptions, in the way that we look at a degree and the person with the degree looks at their degree.
For me, if someone is applying for a role and they have a related degree, I assume that they probably know a little about the theory behind it, but have no clue in terms of how the real world functions. For those with certificates, I generally have an even lower opinion.
Most kids fresh with a degree assume they know just about all there is to know about that field.
The amusing part comes when they find out that even with their degree, they basically come in at the bottom rung of the ladder - a large number seem to think that because they have a relevant degree, they will start off in middle management or a team lead role.
Degree or no degree, when you come to work here, you pretty much start at the bottom and have to prove to everyone that you are actually capable of doing the job we hired you for. That often means working under people without degrees, but ones with years of experience in the real world. For a lot of kids fresh out of uni, that's a bitter pill to swallow it seems.
Moved to http://soylentnews.org/. You are invited to join us too!
I'm not sure how Computer Science courses are at other educational institutions, but my school's Comp Sci program didn't focus much on programming at all. Everything was largely theoretical and we never did much programming at all. If you wanted to fine tune your coding skills, you'd have to do it on your own, or even better on co-op or internship.
Freedom is drinking a beer in the park when you're supposed to be at work.
"has no idea what, for example, the term 'object-relational impedance mismatch' might mean."
I have to say, having gone through a real CS program (quite a while ago now) that covered everything from assembler to algorithm analysis and theoretical proofs, "object-relational impedance mismatch" set off the buzzword warnings.
A Google search confirmed my impression. The problem it describes is (sort of) real, but the term is idiotic. The kind of thing they'd put on one of these newfangled multiple guess CS exams.
A lot of these issues seem to tend from the language of choice in today's colleges. That language being java which is memory managed for you. To alot of the older programming crowd who have used C for years this can seem like a huge flaw and it can be depending on the field. However, alot of programming these days is Web programming and in Java/C# where these skills are uneeded so it is not necessarily such a huge issue. Also, all a Computer Science degree really teaches you is how to learn. There are so many different languages and specializations it is IMPOSSIBLE to learn all the details about everything so you just have to grasp the ability to expand your horizons when needed.
MS cert tests are worse, they measure rote memorization of marketing material.