Actions
Forum Thread Details
  • Replies 23 replies
  • Subscribers 534 subscribers
  • Views 2381 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."

  • Whilst I still do some electronic design, I let my career take me towards embedded software because I initially thought this. After a solid few years away from electronics completely, I then went into a mixed role where I designed some (fancy, not just micro on a circuit board with some LEDs) electronics as well. Just a few years out of the electronics world left a void of missing knowledge that made the electronic design really hard. 

    Behind the scenes I still had the aptitude to work everything out, but in reality, it was not just wiring up little black boxes with metal legs. One thing that was different was that everyone now wants to put a radio in everything and that's where a lot of my older knowledge came in (handy I had some experience in this). The other thing is that, unlike a reference design, it had to meet the emissions standards expected. Plenty of that is down to electronics experience - someone alluded to Apple and their iPhones further up (or down) who took sticking wiggly things right next to other wiggly things and still managed to make a radio transmitter of at least three types out of it whilst meeting all the relevant standards. It's definitely not software engineering making all of that happen.

    What I would say instead is that the entry point for electronics is now lower - integration makes some previously unfeasible devices really simple now; of course we know that because I now have a mains plug that can be controlled by my cell phone. If that's not a first world problem, I worry what is! This means we see more everyday items with a chip in (it started with those musical Christmas cards in the 80s!). 

  • 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.