Actions
Forum Thread Details
  • Replies 23 replies
  • Subscribers 534 subscribers
  • Views 2374 views
  • Users 0 members are here
Related

Is electronic engineering dead?

cstanton

I saw this question on Reddit, and I figured it was a good one to ask the element14 Community as a thought provoking query that may be on new engineering students minds:

"If we consider only circuit design for PCBs, almost all the complexity is moving toward integrated circuits (chip and modules) and/or in code for FPGA or microcontrollers/microprocessors. The role of hardware engineers is still important, because of PCB layout and BOMs, but from the hardware design point of view is almost all already done, just pick a component, read the datasheet and copy the reference design. I’m simplifying, I know, finding the right component is not easy at all, but it seems the hardware engineer role is just reduced to searching and connecting modules. Only IC designers delve into the complexity of hardware design. Do you agree with me or can you explain why I’m wrong, please?

My question arises because I’m considering whether or not to move to hardware design from firmware. Currently, I’ve a master's in Electronic Engineering but I’m working as a firmware designer for microcontrollers."

Parents

  • I believe the border between electronic engineering and software engineering is becoming fuzzy.  Future engineers will not be able to separate the two and specialize in one or the other.  Chips can't cover all of electronic engineering especially human interfacing and not-so-smart sensors.  Reference designs are nice to have, but don't always cover all feature requirements of a project.

    I tell all our new students to learn as much as you can in hardware/software/machining/prototyping/etc. because the available positions require people that have multiple skill sets.  Hiring managers would rather hire a person they don't have to train as much before they become productive.

  • in reply to rsc

    I agree.

    I started with a computer engineering degree which was a split between software and hardware.

    Knowing both worlds made me very useful on many projects.

    The expansion of SOC's to include digital and analog hardware with integrated radio capability keeps bringing these areas together.

Reply
  • in reply to rsc

    I agree.

    I started with a computer engineering degree which was a split between software and hardware.

    Knowing both worlds made me very useful on many projects.

    The expansion of SOC's to include digital and analog hardware with integrated radio capability keeps bringing these areas together.

Children
  • in reply to DAB

    They hire computer engineering students for co-op terms where I used to work and I was pretty impressed with their effectiveness right out of the gate.

  • in reply to dang74

    Yes, when I was in school during the 1970's I was already gainfully employed full time integrating a microprocessor into a laser guided bomb guidance unit.

  • in reply to DAB

    Wow, that's definitely a great example of the strengths and diverse skill set of the computer engineering discipline... and how quickly the students come to speed.  Now of course because I am recognizing the merits of computer engineering I do not want to diminish any personal credit owed to you.  Landing such an important opportunity so early on was certainly due to your hard work and dedication to your field and, also I imagine,the natural gifts bestowed upon you.

  • in reply to dang74

    My first course at the university was a 400 level special engineering course on hardware/software interfacing for a DEC PDP computer. At that point I had a two year electronics degree and experience operating a PDP-11 at work. I made an A for the class. It was just the first of several 400 level classes I took and aced during my freshman year.