You may not have it in the states, but the rest of the world does. I graduated a five-year (160 credit hour) curriculum in "Computer Engineering" which is a bundle of low-level courses (circuts, electronics, assembly, microelectronics, digital integrated circuits), programming courses (c++, c#, object oriented software development), software lifecycle courses (software engineering, project management), math, pure engineering courses (statics, electromechanical systems), and more. It's recognized as an engineering degree by the Engineers Guild, and has given me, above all, the "Engineering Sense" that I apply daily in my development work.
You are right; this is one area the eu is doing better in.
They are points along a gradient of a mixture of CS classes and digital circuits classes.
However, at no point do the CS classes move from theoretical to practical, all the CS classes you end up are the traditional type. So at Davis you're still not getting a "industry programmer" type of CS education, you're just getting academic CS + circuits :)
Your situation sounds similar, with the additional of the two software PM and process classes you mention. Although I'm curious if you think they were helpful, is that a teachable subject?
MIT takes it position as the world's preeminent technical school seriously and in the mid-80s decided this was the single biggest external issue it/the STEM professions had.
Of course the real problem is that non-tech people rely more on political skills and networking to get and keep their jobs. Their day to day work skill set is often quite low.
I found the same thing. I think the reason is that CS in general is easier than engineering/physics (or math) so on average the engineer/physicist is smarter than a CS person (lots of exceptions of course). Just look at the math involved (I've been in the three places btw).
I designed my own soda machine, calculator and even designed/created a real world solution which companies were interested in, though I cant mention because it would be me not anonymous.
I was not a computer engineer, I was a CS student. My school also had computer engineering, but I was not really interested in the EE stuff.
I took all of the Math that engineers take, and I took the Engineering Chemistry and Engineering Physics.
Due to my CS dept being a subset of the engineering dept, the goals were the same. Everything was problem solving. Every class had its set of rigorous problems, which students had to succeed at or they simply would not pass.
I learned Algorithms, internal Operating systems, Complexity, Computation, fundamentals of Programming languages, distributed systems, organization, Computer Architecture, VSLI/HDL, etc. Im sure you get the point.
I personally think I bring a good bit to the table, as do the other few graduates that survived the curriculum.
You very well may find a more well rounded candidate than myself from the non traditionally educated pool, but they will be few. If you lump all CS graduates in the same pool, you are doing yourself a disservice. While yeah, somebody from a Java school may suck. What do you say to a candidate like myself, who really can bring what you need to the table. Do you just cross me off the list because I have a CS degree. If so, I think its you who may need to recalibrate.
Sure pure engineers and physicists may be good programmers, but do they understand the inner workings of a computer? Do they understand complexity, even the basic data structures. I assume you want efficiency?
Do you just cross me off the list because I have a CS degree.
That's silly :) You may have noted from my post that I do hire CS majors.
but do they understand the inner workings of a computer? Do they understand complexity, even the basic data structures.
Yes, usually a lot better than most CS graduates. Because generally speaking in the real world these are engineering problems rather than pure problems.
This is just my observation, but I don't think I am wrong - CS majors are generally worse programmers (and usually more full of themselves, but that's another matter) than CS engineers.
I would consider you (based on your post) an engineer; as you explain, you were part of the engineering dept.
(that's not to say CS majors are all bad - I've met some extremely good ones. The problem is that the majority of CS is taught as a pure subject with a smattering of applied theory. There is a distinct lack of problem solving involved. Traditional disclaimer: YMMV)
Also I should point out that being an engineer does not automatically make you a great programmer. Clearly you need an interest, an amount of aptitude and the ability/willingness to learn the pure subjects (if they were not part of your degree). The last of those isn't all that important - to be a good programmer you only need the amount of pure theory that is required (and you learn to pick it up as you go) - this is a common trait of all engineering.
Curriculum wise UIUC actually does an excellent job of addressing this issue. I imagine other schools are similar. We basically have our three core theoretical courses and everything else involves programming. Every course that isn't a theory course involves several significant programming assignments. For example, in our networking course the final programming assignment (in C) is to implement TCP over UDP. We have a seperate course called Programming Studio that is required. The entire course just focuses on learning programming well. And students can opt to do a large software engineering project instead of a thesis their senior year (the vast majority do software engineering, not a thesis).
I think all these measures help, but despite the heavy emphasis on programming, a lot of graduates are still horrible programmers. I think the root cause is that we are still learning how to teach programming well; we've had a much larger head start on learning to teach mathematics.
> you were expected to be able to largely pick that kind of stuff up by yourself.
I think the main problem lies here; because a lot of people are possibly too lazy to do this...
In our particular case we would check out the degrees people had done (just Reading the websites) to get an idea of what they had learned - I only really do that for new graduates though, it's less relevant to more experienced people.
I've employed a goodly few programmers - invariably the least good are CS majors, the best are usually engineers or physicists.
The reason is that CS is a theoretical degree, and far too many people do it assuming they will become a "programmer of value", rather than a potentially important CS researcher. I've had applicants bore be with details of compiler theory they learned, or algorithm programming they worked on and so forth. All interesting stuff I admit - but the question of "can you write a program" is skipped around :)
Compare that with a degree like engineering (any engineering really). They have learned one skill, that is driven home over and over: how to solve problems. The actual knowledge from their degree is irrelevant (you don't generally learn all that much at university) it is their analytical and solution skills that are key.
There is nothing wrong with this setup. The problem is that CS is treated like an Engineering degree rather than a Mathematics major. Really it should be the latter; if you wish to do research in CS, teach it, work in sort of related fields (CS Majors make good traders, for example, like mathematicians) then CS is the way forward. If you want to be an industry programmer it isn't.
What we need is an intermediary; an Engineering degree that hands you some basics of CS and a whole lot of critical thinking. The whole aim of a degree like that is to point you in the right direction and let your interests develop into a career. This needs to replace CS as the majors for most people - and I think, actually, it would make them happy :)
Hackers are an odd exception; personally I think a good hacker would get much from any of the degrees - theoretical or not - though it is worth remembering that a good hacker will generally be a good programmer anyway because they can hack around, and solve, problems.
(Just to point out: I disagree with all of what Zed has to say about CS itself - clearly there is a lot to learn there, if you go for the right reasons)
University is a great choice for someone to further their education; not because it will teach you much (if you expect university to be the peak, or even the start, of your education you've failed already :P). But because it teaches you the ability to learn for yourself, think critically, break the discipline cycle that school drilled into you, get drunk, make important friends, find people to bounce ideas off.. the list goes on. Somewhere down the bottom is "sit in lectures and learn stuff". Learning is easy; the rest is far more important! :)