Originally posted by: schizoid
Originally posted by: gopunk
Originally posted by: schizoid
Sigh.
You people, I swear....
I got a BS in CS. What did that qualify me to do? Nothing, really. I didn't know any Java (still really don't), my C++ was weak, and I did zero programming for Windows. So, what could I do?
I WAS A FREAKIN' SCIENTIST, YOU DOLTS!
If you wanna be a "programmer", go get your moms to buy you a Barnes and Nobles giftcard. If you got the chops, you'll get a job.
If a degree is important to you, get a CS degree. It'll help, but you'll still need the chops to get (and keep) a job.
Realize that most of your hardware classes are meaningless. I tiny fraction of people actually do anything even remotely related to hardware. Most EE people end up doing systems level stuff (controls, etc). Those jobs exist...so, in that sense, maybe EE is the way to go.
But as for a "ranking" of EE vs. CS vs. CSE, there really isn't one. I'm getting my PhD in CS because I enjoy being a scientist. Being a code grunt, or a engineering monkey has no appeal for me. So, regardless of whether you want to do software or systems, if you like being a scientist, there's no reason not to get a CS degree.
The reality is, 95% of your coursework will be meaningless in the context of your job anyway. Employers want to know that you're a hard worker, that you can pick up new ideas, and that you can work in a team environment and follow directions.
So, yeah...and besides...engineers are grunts.
what school did you get your BS in? i completely understand and agree with your sentiments about the science part of computer science, but it seems to me that most modern departments would give their graduates at least some proficiency in prgramming.
Ameesh? Take notes. You could learn a thing or two from Gopunk.
I
do know how to program. I coded up a freakin' command line interpreter for the lambda calculus in ML. Does this help one get a job? No. Not in the least. I can also code in Prolog, Lisp, and a host of other things that don't really have any practical applications outside of academia (I'm okay with this, seeing as I don't
want to be outside of academia. But I digress...
I've learned, at one point, just about every nook and cranny there is in C++. I don't really remember much of it, and, honestly, the last time I tried to use templates, I think the code exploded in my face.
I can also deal with complex Markov chains and have been known to solve the occasional MMp1 queuing model.
As for Java, it was simply a matter of timing. My first ever CS class, in the fall if 1996 was in Pascal. It was switched to C approximately 6 months later. I didn't actually "get" to C++ until the end of my sophomore year, in a data structures class. It was almost a year later, in a programming languages class, that we covered serious C++ (this was winter 99). All my networks classes were in C or C++. A year after I'd taken them, they were changed to java.
UC Davis, where I went to school, won't touch Windows.
My senior year, I took a grad seminar in database integration, and I had to code up a Java front end for the XML-ql query engine. Swing wasn't even standardized at that point. I just took some other code, hacked away at it until I got it to vaguely do what I want.
This semester, (at USC, where I'm doing my PhD) I modified some agent code that was in Java.
So, would I say I
know Java? No, not at all. Could I learn it as well as anyone else on the plannet in a matter of days? Sure. Will I ever bother? No, not likely.
Like I said, I'd rather tinker around with POMDPs.