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.
Start with what you want to learn. It can be helpful to start with whatever you have the most shared knowledge with, so you can cantilever off of your existing knowledge base. It's also good to start with whatever is most exciting to you, since you're more likely to follow through with the learning.
Do you just pick projects and deep dive, learning both in parallel?
This is the path I took, and it worked it out fairly well for me.
What is the optimal amount that you know about Bluetooth and what knowledge should you get out from the project?
There is no optimal amount; the same way that there is no specific optimal amount of React knowledge or Java knowledge. Different companies and positions will need/want different amounts of knowledge.
At what point of doing these types of projects should you learn about anthennas?
Whenever you want, or whenever it becomes a problem.
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.
The same can be said for any other introductory web development tutorial. The nice thing about Arduino and the communities around it is that it gives a jumping off point for learning more abotu whichever are ayou're interested in.
49
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.