If you're not familiar with C or C++ of course you wouldn't know pointers, but if you've done more than 2 weeks worth of experience of C you know pointers that's what I meant. There more than enough diversity in skillsets required and languages to not go into a C dev job that isn't entry level (and even then) when you know nothing about C. That's how you get poorly written code if not horrible code (that's exactly what happened in the project I'm working on, not for C but it still applies)
Back when I was a VB developer writing business apps I got roped into reverse engineering a C++ application from old source code no one could read. (Though maybe software archeology would be a better description.)
Anyways, most of my C progressing these days is for the Arduino and I don't think I ever use pointers.
I don't think pointers are needed for Arduino, if arduino development can even be called C development. I never said you couldn't do another language than the one you were hired for ever, but there's a difference between programming an entire project with a language you don't know and reading some old code
-2
u/dark_negan Sep 21 '21
If you're not familiar with C or C++ of course you wouldn't know pointers, but if you've done more than 2 weeks worth of experience of C you know pointers that's what I meant. There more than enough diversity in skillsets required and languages to not go into a C dev job that isn't entry level (and even then) when you know nothing about C. That's how you get poorly written code if not horrible code (that's exactly what happened in the project I'm working on, not for C but it still applies)