Calling all CS majors....

[mugs]

Originally posted by: spidey07
That's fine. Nobody cares what classes you took or take as long as you get the degree. If it's a requirement...I'm sorry if if was a jackass earlier...

Nobody cares what classes you took, but you do learn in those classes, and that is pretty important.

 

[mugs]

Originally posted by: FoBoT

Originally posted by: mugs

It makes me want to punch babies. Literally.

but you wouldn't , would you? you wouldn't actually punch a baby

I would and I have. Literally.

 

[BigJ]

Originally posted by: Oiprocs

Almost, but not quite. I reread my original post and I should have made it clearer. My apologies to all.

The classes I listed are ones that would be required by a CS specialization. However, due to the fact that some of the classes have been pointed out as negligible by some friendly posts, I decided that I would rather specialize in Network Systems. That appeals to me just as much, and after the required courses for a Network specialization, I will have 7 free electives to use in any manner. I'll most likely use 4 or 5 of them on CS courses that have been mentioned as useful by responses in this thread.

If you have truly free electives, do what spidey said in going with Comm. and Bus. courses. Spidey was absolutely spot on with this. Learn how to sell yourself and communicate well. That's going to make the difference with getting the job. Also try public speaking.

With the Network Specialization, what do you exactly mean by that?

 

[slpaulson]

Originally posted by: spidey07

Originally posted by: BigJ

Originally posted by: spidey07
It really is amazing how people in college place so much on what class, what professor they had. Like it's important. Like this really matters.

You can believe what I say or not...but what classes you took, what professor you had is completely irrelevant. Even if I can't spell.

-edit-
Be well rounded in basic computing, so many grads in CS can't grasp this simple concept.

Here's a couple of simple concepts and pieces of information you can't grasp:

-He's not a CS major. He's an EE major with a software systems specialization (he actually updated this to a Networks specialization later in the thread).
-People are only talking about professors in the context of how much you like the class and how difficult it can be. Would you rather take a class with the dick professor who only gives 1 A out to the entire class, or would you rather take the class with the professor who is amicable with his students, makes the topic interesting and fun, and makes you look forward to going to class?
-Since he has to specialize, he's required to take the CS classes. He can take Comm, Business, and whatever the hell else he wants on his own time, but these are classes he HAS TO TAKE for the specialization.

If you're going to talk down to people, pull your head out of your ass for a minute and actually read the posts in the thread.

That's fine. Nobody cares what classes you took or take as long as you get the degree. If it's a requirement...I'm sorry if if was a jackass earlier...

Basic Data Structures and Object-Oriented Design
-not suited for a EE-
Mathematics for Algorithm and Systems
-better suited for a EE-
Advanced Data Structures
-helpful, but not really related to EE-
Design and Analysis of Algorithms
-helpful in computing-
Principles of Computer Operating Systems
-not so helpful in EE-
Introduction to Computer Architecture
-essential to EE-

I really am sorry for being rude. Computer Architecture would be a nice, single class to add to augment the understanding of computing, followed by Design and Analysis of Algorithms. These classes will round out a EE.

Basic Data Structures and Object-Oriented Design are not suited for a EE, but advanced data structures would be?

If you're going to do some type of programming, you really should at least take some sort of class on data structures in my opinion.

 

[oiprocs]

Originally posted by: spidey07

Originally posted by: BigJ

Originally posted by: spidey07
It really is amazing how people in college place so much on what class, what professor they had. Like it's important. Like this really matters.

You can believe what I say or not...but what classes you took, what professor you had is completely irrelevant. Even if I can't spell.

-edit-
Be well rounded in basic computing, so many grads in CS can't grasp this simple concept.

Here's a couple of simple concepts and pieces of information you can't grasp:

-He's not a CS major. He's an EE major with a software systems specialization (he actually updated this to a Networks specialization later in the thread).
-People are only talking about professors in the context of how much you like the class and how difficult it can be. Would you rather take a class with the dick professor who only gives 1 A out to the entire class, or would you rather take the class with the professor who is amicable with his students, makes the topic interesting and fun, and makes you look forward to going to class?
-Since he has to specialize, he's required to take the CS classes. He can take Comm, Business, and whatever the hell else he wants on his own time, but these are classes he HAS TO TAKE for the specialization.

If you're going to talk down to people, pull your head out of your ass for a minute and actually read the posts in the thread.

That's fine. Nobody cares what classes you took or take as long as you get the degree. If it's a requirement...I'm sorry if if was a jackass earlier...

Basic Data Structures and Object-Oriented Design
-not suited for a EE-
Mathematics for Algorithm and Systems
-better suited for a EE-
Advanced Data Structures
-helpful, but not really related to EE-
Design and Analysis of Algorithms
-helpful in computing-
Principles of Computer Operating Systems
-not so helpful in EE-
Introduction to Computer Architecture
-essential to EE-

I really am sorry for being rude. Computer Architecture would be a nice, single class to add to augment the understanding of computing, followed by Design and Analysis of Algorithms. These classes will round out a EE.

Haha, I didn't think you were being rude. When a lifer speaks to me, no matter how harsh, I always believe it's because they know better.

For real though, you're right about classes in other disciplines. If you can hack with the best of them, but have no idea how to present yourself, you're not really standing out. I should have mentioned I'm more street smart (yeah, I'm thug ) than I am book smart.

Anyways, I'm going to narrow it down to about 4 from the following list:

Introduction to Computer Architecture
Computer Organization and Systems Programming
Basic Data Structures and Object-Oriented Design
Compiler Construction
Computer Networks
Principles of Computer Operating Systems
Mathematics for Algorithm and Systems
Design and Analysis of Algorithms
Advanced Data Structures

As for Network Specialization, these are the classes that I will be taking for that:

Probability and Random Processes for Engineers
Data Networks I
Data Networks II
Queuing Systems: Fundamentals
Queuing Systems: Computer Systems and Data Networks

 

[darthsidious]

I'm an EE, and my advice is this : think about what kind of job you want after graduation, and decide what additional classes to take based on that. It seems that for an EE, you're thinking of taking farily specialized CS classes, like advanced data structures, compiler theory, etc. They're great if you want to work in CS, but not so much if you want to work in EE. Your time might be better spent taking classes closer to/in EE. If you want to work at the hardware/software interface, I would recommend learning assembly/low level programming, and some microcontroller classses, and computer architecture. If you want to do circuit design, you're better off taking more circuit electives.

P.S. : Most of my knowledge of digital/microconrollers is second hand - I'm almost purely an analog guy

 

[darthsidious]

Originally posted by: MrDudeMan
I'm a Computer Engineer and I'd squeeze Controls in there if you can. It is one of the most beneficial classes for all engineers.

Your later classes will all be extremely relevant to what you do for a living should you pursue the engineering route as a career, so choose wisely. Signing up for a course on compilers is a no-brainer by the way. I'd drop Design and Analysis of Algorithms.

Oh yeah.... classical control/feedback theory is vital, esp for EE's. Infinitely so if you want to do anything analog, and even in digital, knowledge of feedback techniques is valuable. People have told me that they even use control theory concepts in programming, but I have no idea about that....

 

[oiprocs]

Originally posted by: darthsidious
I'm an EE, and my advice is this : think about what kind of job you want after graduation, and decide what additional classes to take based on that. It seems that for an EE, you're thinking of taking farily specialized CS classes, like advanced data structures, compiler theory, etc. They're great if you want to work in CS, but not so much if you want to work in EE. Your time might be better spent taking classes closer to/in EE. If you want to work at the hardware/software interface, I would recommend learning assembly/low level programming, and some microcontroller classses, and computer architecture. If you want to do circuit design, you're better off taking more circuit electives.

P.S. : Most of my knowledge of digital/microconrollers is second hand - I'm almost purely an analog guy

Well to be honest I know that I like computers/programming/software, but I've done research on the fields within EE and most of what I find is they design circuit boards/processors, deal with DSP and communications, etc.

I know that I like communications, and I think that working to design/build more efficient methods of transferring data on a global aspect. While it would be interesting to work on the hardware needed for that, I also want to be able to work with the software and coding that has to go with such a device. I'm planning on taking a 3-series course on communication systems, so maybe you could point me out to a few other EE course that would help me with this task. I definitely want some CS skills on hand though.

EE Courses

What do you do in your work?

 

[Casawi]

Make it a dual degree then !!!!
Why not get an extra line of writing on your piece of paper

 

[darthsidious]

Originally posted by: Oiprocs

Originally posted by: darthsidious
I'm an EE, and my advice is this : think about what kind of job you want after graduation, and decide what additional classes to take based on that. It seems that for an EE, you're thinking of taking farily specialized CS classes, like advanced data structures, compiler theory, etc. They're great if you want to work in CS, but not so much if you want to work in EE. Your time might be better spent taking classes closer to/in EE. If you want to work at the hardware/software interface, I would recommend learning assembly/low level programming, and some microcontroller classses, and computer architecture. If you want to do circuit design, you're better off taking more circuit electives.

P.S. : Most of my knowledge of digital/microconrollers is second hand - I'm almost purely an analog guy

Well to be honest I know that I like computers/programming/software, but I've done research on the fields within EE and most of what I find is they design circuit boards/processors, deal with DSP and communications, etc.

I know that I like communications, and I think that working to design/build more efficient methods of transferring data on a global aspect. While it would be interesting to work on the hardware needed for that, I also want to be able to work with the software and coding that has to go with such a device. I'm planning on taking a 3-series course on communication systems, so maybe you could point me out to a few other EE course that would help me with this task. I definitely want some CS skills on hand though.

EE Courses

What do you do in your work?

I gotta run to work, so I'll write more later. In my work, I essentially design analog IC circuits to make highly integrated systems. It's a great job for the most part - the only downside being that if you're the type of EE who likes to tinker in the lab, you don't get to do much of that in my job - almost all my time is spent with paper + pen, or on a circuit simulator.

If you like communication systems, take some communication theory/ information theory - they are vaulable both on the programming end and the EE end. You need to be happy with math though...

 

[sdifox]

What? no Theory of Computability? I think that is the best course ever. Hard as hell, but practically the only think I remember. Software Engineering is good if you can shovel. Computer graphics is pure math, do that if you like math. Databse is ok. You don't have math requirements? CS is really applied math.

 

[oiprocs]

Are analog and digital both widely used today? Why is analog said to be much harder?

 

[darthsidious]

Originally posted by: Oiprocs
Are analog and digital both widely used today? Why is analog said to be much harder?

Yes. Digital Electronics have become very pervasive recently, but analog will always have a market - if for nothing else, because real-world interfaces have to be analog. A modern trend is to leverage both analog and digital electronics on massive SoC's (System on Chip) to perform a task that traditionall required multiple chips. For example, I'm working on a chip that combines most of the functionality of a cellphone on a single chip - it has lots of analog and digital.

Thereare a lot of digital jobs,compared to the number of analog jobs, but the supply pool for analog is even smaller - most people don't like to do it for some reason. This means that if you're a good/competent analog designer, finding a job is not too hard - infact, most companies are forced to hire people from abroad (like me) and pay for visa processing and stuff (which can be expensive), becauase they can't find enough local candidates (I did study in a US university though).

As for analog being harder than digital - I think that's a tricky question. Certainly, the design tools for digital design are much nicer and effective, and thus even a not-so-good designer can churn out decent designs. In analog design, if you're not good- it will clearly show in your designs, even if they are basic. However, great digital digital design is as hard as great analog design - but the challenges are at a higher level - algorithmic vs transistor level/details. For example, a digital designer would worry about executing a task with the fewest instructions/clock cycles, while analog designers worry about transistor nosie and feedback loops going unstable, for example

 

[oiprocs]

So in your work you do a analog design? Is there an analog signal processing like there is digital signal processing? Are those just part of designing?

 

[sdifox]

Originally posted by: Oiprocs
Are analog and digital both widely used today? Why is analog said to be much harder?

Digital = State limited Analogue

 

[piasabird]

Database is where it is at man. That goes along with networking. Most programming is done by people in India. It is nowhere's ville man.

 

[darthsidious]

Originally posted by: Oiprocs
So in your work you do a analog design? Is there an analog signal processing like there is digital signal processing? Are those just part of designing?

Yes, I mostly do analog design ( though we often have to interact with digital blocks, and gradually, some digital design style techniques have creeped into analog. Infact a lot of the newer papers being published use digital style sampling/error correction to improve analog accuracy). There is analog signal processing (mainly filter design), but a lot of it is being phased out, because IC analog components have fairly bad accuracy, and take up lots of area. DSP is predominant in the signal processing world.

While analog filters are a part of design, I wouldn't call DSP so. In most places, digital designers do digital designs in verilog or something, while they hire specialist DSP designers, who typically develop algorithms for filtering etc. on something like Matlab. Eventually, these designs/algorithms are written in a high-level language and run on a special purpose microprocessor called the DSP core (typically bought from a company that specializes in making microprocessors optimized for DSP -type applications). So, it's mostly math and programming, though like all groups on a design, it's always good to know something about the other blocks so that you can communicate effectively.

 

[oiprocs]

Hmm. I see. Well all the advice you gave is damn helpful, I learned a comparable amount of information to the time I spent researching.

I think I'll take a few CS classes, probably 3, so that I have some kind of computing skill. I'll use the rest of my electives on whatever interests me in the course guide. Hopefully I'll take something I enjoy and decide to pursue it.