3 ms·
>but I kind of doubt I could be very intelligent about it without a bunch of catching up. I doubt you'd need to catch up because of expired knowledge. Rather t
by carlmr 3y ago
>but I kind of doubt I could be very intelligent about it without a bunch of catching up.
I doubt you'd need to catch up because of expired knowledge. Rather things you forgot or areas that you didn't deal with yet.
I think embedded can have a lot of depth if you get into certain details.
There's basically no framework churn like in webdev, though. C and C++ are still very much current.
Rust is becoming more of a contender, but still not common.
- edanm 3y ago> C and C++ are still very much current. So it's interesting you say that. I worked extensively with C++ back then, and I did have occasion to do a few small C++ projects about 10 years ago, and C++ seems to have changed quite a bit. It was actually really impressive. I'm not saying it would be very hard to learn the differences, but I definitely needed a primer back then of "here's how C++ has changed", because code really did look different in some ways.
- carlmr 3y agoC++11 was quite a break, C++14 very minor, C++17 a little bit more, but not as major. C++2x is doing a lot of changes, but I haven't seen much of it in the embedded world yet. Mostly because C++17 is still considered new-ish in most safety-critical realms. But say you have some C++<11 experience I think you would need a few weeks to get up to speed max.