| ▲ | qazxcvbnmlp an hour ago | |
As someone who currently does embedded, and transitioned into it with extremely little professional experience. You need to be able to demonstrate that you understand the tradeoffs that come with embedded and how you can provide value to someone who would hire you. Web development is very much a continuous integration easy to fix bugs kind of environment, in embedded bugs can have real cost. As someone who frequently hopped around across different domains, the key is demonstrating that you understand their problems and can provide value. Also, being curious helps. Also, today with AI am not sure how much native development is going to matter. A handful of best practices in an already set up project plus an AI agent is gonna spit out very workable code. Right now the problem space is very much about reasoning about the larger system, de bugging stuff, thinking about how pieces work together, going in the lab and connecting debuggers so that they agent can do stuff to the hardware, etc. | ||
| ▲ | zergrush 31 minutes ago | parent [-] | |
> Right now the problem space is very much about reasoning about the larger system, de bugging stuff, thinking about how pieces work together it's already being done without humans, you are already far too behind here | ||