Who actually makes comuter Hardware Electrical or Computer Engineers

Scotch77

Gawd
Joined
Jul 27, 2005
Messages
769
Who actually makes the computer hardware. Such as motherboards and memeory and stuff like that. Ive heard different stories from different people, same say Electricle engineers make the hardware and Computer engineers do the saftware. Some say computer engineers make the hardware and computer scientists make the software or code the hardware.

who are those who make the hardware?
 
It is a little of both...

Eletrical/Computer Engineers are basially the same thing, when it comes to what they can do. Electrical a little more hardware, Computer a little more software, but more than likely the term can be internchangable. Both do about the same amount of low level coding though, such as some assembly langague, and both do PCB layout for your parts. Including the soldering and routing of those wonderful traces from C1 to U1, you know the idea. IF you go to your local college, the two degrees are probablly so closely related that they may only offer one, or combine them, or a double major is quite easy to obtain. But in short Electrical/Computer Engineers make the hardware, thats usually their primary function.

Most of the Software is done by Computer Scientist, IE CS majors, as they are basically focused on software. A wide range of software, but typically someone who is going to do a CS major thinks of the big scale, high-level programming, at the operating system level.

Hope that helps, wanting to decide what type of degree you want to get?
 
No I am already a CE student at Manhattan College here in the Bronx. Ive just had People tell me things online, saying it was the EE who build the hardware and the CE sat their and coded. I know many other memebers here are also Engineering majors, so i thoght id ask.

yes my school pretty much gives a degree in Electrical/Computer Engineering
 
Electrical Engineers design microchips and various other systems. I went to school with someone who is one of the world's leading experts now in microwave communications. He took Electrical Engineering upto PhD level. He designs microchips, mobile phones as well as the satelite missile guidance systems used in the first gulf war.

My other friends who took computer engineering tend to design AI programs. Although they do some hardware they tend to be more into the programming side of things.

Good luck with your future.

Skye

(\(\
( -.-)zzZ
o_(")(")
sleepy jazz bunny
 
The lines between programming and hardware get more fuzzy all the time. EE's write the code that becomes specialized processors (Ethernet, etc.) because they understand the DSP, signal integrity issues, etc. that must be dealt with in those types of products. Software programmers have to be aware of the hardware to use it more effectively. Even board design guys have to throw down the occasional PAL (programmable array logic) to properly interface ASIC's that refuse to play nice together, which of course requires code to operate.

Two of the last bastions of pure "analog" design - RF and power supply design - are now going more and more digital. I've seen "compiled" RF ASIC's that aren't put together the "old fashoned" way....rather described with some type of code (Verilog-ish) and then loaded on a target chip. Power supplys are now more often than not "switching" supplies, rather than basic linear supplies, and there's tremendous advantages to using uC's to run that whole show.

Bottom line is that today's EE's and "software" programmers have to know more than little about each other's work, if they are to be effective.

Regards - B.B.S.
 
BlindedByScience said:
Bottom line is that today's EE's and "software" programmers have to know more than little about each other's work, if they are to be effective.

Regards - B.B.S.


QFT...

Most EE's will have to write some Verilog or hardware description language. Some EE's get suckered into low level firmware.

BBS - You working from home during the cube crunch?
 
Absolutely right...

I am doing the design work for a custom ASIC. I have used ,mainly Verilog because it allows more control over the exact hardware implementation of the high level language. I have also in some cases used some VHDL which reduces development time on non-critical system blocks.

On very critical (mainly high speed) areas of the chip design, each gate is designed specifically for the job it is required to perform. This is a very slow process and is only used where absolutely necessary.
 
Back
Top