Coding...is engineering. Put the world behind the wheel of a car and they can make it go places. This...does not make them an automotive mechanic.
What a terrible analogy, just because you know the car's firmware doesn't mean you know how to properly diagnose something not related to the electronics (worn wheel bearings or suspension components) let alone how to diagnose or repair.
While I agree coding serves engineering, it's always funny to me how quick people want to use the term 'engineer' when it suits them, but then developer when things go wrong and accountability is on the table. Furthermore, engineers tend to have licenses in their respective fields, something I don't personally agree with, and to this day I have yet to see the same in IC roles.
Sidenote: As a former tech (mechanic) there were times when you would question not just an engineer's competence, but their entire sanity given how something was deployed, and needed to come up with a work-around for it to function correctly; which is why I think coders (at least the proficient ones) are more like techs.