last Thursday at 5:12 PM
I'd say just do it. You have been in the industry for 15+ years and you surely know how to network/do interviews. I feel that you are just hesitating or wait for some confirmations. I wrote similar posts so that's my guess, but please criticize me if I'm wrong.
My point is, whoever has actually done the transition, their experience may not really help you a lot. They might have a cousin who actually refers them to the company; They might have worked 10 years of embedded projects as a hobby; They might be lucky because 5 years ago there were a huge opening somewhere. I heard of a metaphor about elevators -- Several people ride an elevator to floor 100, and a reporter asked them how they get there -- one of them said he did 1,000 push-ups, another said he read 2 books, and a third said he bumped his head against the elevator's walls.
Those experience might be very well relevant, or not. But above all, copying others' experience, in THIS market, probably doesn't work. Now that you are 6 years senior than me regarding SWE experience, I think you already know what to do -- just do it.
last Thursday at 2:45 AM
There are two issues: 1) transitioning your skills, and 2) persuading someone to hire/pay you for your new skills.
Transitioning your skills is possible. But embedded is a different world and a different mindset. You a lot less RAM and a smaller CPU. You may have hard deadlines - the right answer can be wrong if it's too late. You may have multiple threads that have to share data and not corrupt it, no matter what order events occur in.
In the worst case, you may not have logging available at all, and you may not have a debugger. (I think the worst I ever had to do was attach a logic analyzer to the address bus, triggered by a specific address, and then use it to look at past memory addresses in order to figure out what path of execution had got me to the point of the crash.)
So, yeah. It's a different world. Learnable, but different.
Getting someone to believe you can do it enough that they're willing to pay you: I don't have great advice there. I spent almost my whole career in embedded. It seems to me that it's easier to get from there into, say, desktop programming, than it is to go the other way. Your best bet might be to emphasize your native development background, and count on there being a shortage of embedded people.
last Thursday at 1:10 PM
You can get started learning with any of the amazingly cheap and powerful ESP32, Raspberry Pi, Raspberry Pi Pico, and Arduino stuff out there, along with dirt cheap TANG FPGAs, etc. Get some projects under your belt in your free time. Start with the canonical blinking of an LED, and step it up from there.
last Thursday at 5:21 AM
I've done both over my career (as well as some other stuff.)
While they are very different, if you know C, it's not hard to transition.
Getting a job in the embedded space though is obviously a lot harder than web. There are simply fewer jobs to be had. Doing some personal projects in the space may reawaken your C skills, and help demonstrate competence.
Good luck!
last Thursday at 4:17 AM
You can embed quickjs then write js.
last Thursday at 3:48 AM
[flagged]
last Thursday at 2:39 AM
[flagged]
last Thursday at 2:09 AM
[flagged]