Difference between "firmware engineer" and "writing embedded code"?

it seems to me that "firmware" and "embedded code" are used interchangeably, but not sure if there is a difference between the two.

Can anyone explain the difference, if at all?

Kind of related to my other thread, but: if embedded code is indeed different than firmware, what skills (courses, course track, etc.) are needed to "write embedded code"?

I wanted to give this its own thread since I didn't want it to get lost in the shuffle in the other thread. Would appreciate a solid answer on this and so wanted to highlight it with its own thread.

Thanks

I would say that firmware is a very specific type of embedded code. But embedded code would be applicable to many other applications that wouldn't be classified as firmware, such as PLC programming, or basically ANY programming done for an embedded application, even if it's still 'normal' programming such as writing windows software, it's still embedded code if it's running on a windows machine embedded for a specific application.

In tech speak the word embedded means little more than 'designed for a specific purpose' you'll probably find fewer people going for a firmware engineering degree as opposed to an embedded engineering degree, the work force doesn't like 'one trick ponies' so much as someone that may be more versatile.

The term firmware has been blurred so much in recent years it's become embedded engineering, because simply limiting it to firmware distorts the meaning of firmware. Which is solidly defined.

https://dictionary.reference.com/browse/firmware

If you read the definition of firmware I think you'll see why the term ebedded code is used now. Firmware is technically only ROM memory. Modern 'firmwares' are based on flash memory now so the 'firm' is really gone out of the modern application of embedded coding, so the words are evolving to suit.

I'd say the bulk majority of all uses of the word firmware today are incorrect to the original definition. It's elegant proof that language evolves.

Yep there a lot of people calling there code firmware because it's not open to let the user make changes LOL

Or can it be defined as a code inside chip, which is hard to replace?
Like firmware of an MP3 player or mobile phone.

I agree with the evolution of the term. You can ask them what they think the difference is?

Take your microwave. It was mask programmed. A mistake could be very costly. One particular set top box for the DTV system in the US apparently had an audio design error in the mask programmed ASIC. They, fortunately were able to move that functionality to off board chips and use that for production. The team that wrote that wrote "embedded code". They have more accountability.

Next team writes router firmware. They released a version of the firmware that on odd months of the year the password would display. They tell the owners about the problem and release a new "firmware version" and suggest that they update their routers. This is the embedded engineer.

Now, there is another product which can be updated, but only though the factory JTAG programming tools. This needs the services of an "embedded engineer".

My take is that the "embedded engineer" has more responsibility than the "firmware engineer", but the firmware engineer also has to worry about bricking a device and updating a device without messing up the previous settings. He may have to worry about exporting and importing settings etc.

My take is ask. The above is an opinion. With the creation of Flash, the early definitions blurr.