It depends. If there is a component that evaluates the sensor status through some form of runtime and then regulates the temperature based on that, you could call it coding (I don’t think this is ever done since it has no practical use). Else, it’s just system architecture.
Of course, there is some overlap within those areas because they both rely on logic, but the latter would not be considered coding.
If you study CS, you will most likely have a course that gives you a basic idea about system architecture and if you study engineering, you will probably have to code some small thing or at least have a course on the basics. So yeah, not entirely distinct.
Imo, that’s coding, just analog LOL
“If” Sensor reached temperature. -“then” Cut power.
Disclaimer: I have ZERO coding knowledge of any kind.
It depends. If there is a component that evaluates the sensor status through some form of runtime and then regulates the temperature based on that, you could call it coding (I don’t think this is ever done since it has no practical use). Else, it’s just system architecture.
Of course, there is some overlap within those areas because they both rely on logic, but the latter would not be considered coding.
If you study CS, you will most likely have a course that gives you a basic idea about system architecture and if you study engineering, you will probably have to code some small thing or at least have a course on the basics. So yeah, not entirely distinct.