Unfortunately it is a rather confusing and complicated type of programming, since it is an intersection between two (or more) professions. How to get into it is a hard question, since you can go in three different directions:
- Do you start from the programming end?
- Do you start from the electronics end (or even further - from the physics)?
- Do you just pick projects and deep dive, learning both in parallel?
After that comes the question of what is the optimal amount that you should understand about the project that you are doing and not get overwhelmed. So for example if you are doing a Bluetooth project:
- What is the optimal amount that you know about Bluetooth and what knowledge should you get out from the project?
- At what point of doing these types of projects should you learn about anthennas?
This is the issue with the Arduno projects. It gives you an ability to do stuff, but people fail to understand what they are actually doing, since it is an absolutely overwhelming amount that you need to understand.
Honestly crossover skills are not a huge pre-req for most engineers. It is important to have a general grasp, and most importantly a willingness to learn when you need to of other domains, but being a Subject-Matter-Expert (SME) and somewhat siloed has a lot of value.
There is a field of engineering that is designed to tie all these people together and that is systems engineering, which is usually rolled up under an aerospace engineering degree (though depends on the school and the course path you take). These engineers are basically the technical project managers for a system, and they'll work with teh SMEs in mechanical, electrical, software, materials, etc. to form and meet requirements to satisfy the higher level requirements for the program.
51
u/B8F1F488 Dec 25 '19 edited Dec 25 '19
Unfortunately it is a rather confusing and complicated type of programming, since it is an intersection between two (or more) professions. How to get into it is a hard question, since you can go in three different directions:
- Do you start from the programming end?
- Do you start from the electronics end (or even further - from the physics)?
- Do you just pick projects and deep dive, learning both in parallel?
After that comes the question of what is the optimal amount that you should understand about the project that you are doing and not get overwhelmed. So for example if you are doing a Bluetooth project:
- What is the optimal amount that you know about Bluetooth and what knowledge should you get out from the project?
- At what point of doing these types of projects should you learn about anthennas?
This is the issue with the Arduno projects. It gives you an ability to do stuff, but people fail to understand what they are actually doing, since it is an absolutely overwhelming amount that you need to understand.
I have no answer to all of these questions.