My understanding is that hardware companies usually alternate generations: one for performance, one for power. It seems like this is the balance that makes the market happy.
A lot of it is in the design stage tbf. If features/UI can be cut or simplified then it can make a big difference. Performant code is good and the tech stack you choose also matters.
I started with raspberry pi zero projects. Specifically projects that make use of various GPIO hats like cameras, displays, speakers, etc. At that level, things are still very abstract compared to bare-metal firmware, but you learn some of the basic principles of I/O. Next plan is to read up on circuit design, and start doing more projects with arduino-controlled breadboards.
I’m training to work in hardware currently. Its my hope that there at least, people still care about min-maxing power vs performance.
My understanding is that hardware companies usually alternate generations: one for performance, one for power. It seems like this is the balance that makes the market happy.
It’s really hard.
Wasn’t expecting it to be easy. Think it will be much more rewarding though. Already has been thus far.
Edit: wait, that was a pun, wasn’t it?
No, it was a palindrome.
Any recommendations for a beginner or hobbiest? I’m going to assume it goes beyond writing more performant code
A lot of it is in the design stage tbf. If features/UI can be cut or simplified then it can make a big difference. Performant code is good and the tech stack you choose also matters.
I started with raspberry pi zero projects. Specifically projects that make use of various GPIO hats like cameras, displays, speakers, etc. At that level, things are still very abstract compared to bare-metal firmware, but you learn some of the basic principles of I/O. Next plan is to read up on circuit design, and start doing more projects with arduino-controlled breadboards.