He didn't explain, but the reasoning is that an embedded developer can work for years on projects that dont' have a screen, so there's nothing to print to.
I once found myself in a similar situation. After 2 years of working on an embedded C project (without a screen), I needed to print something. I found out to my horror that I didn't know how to do it - I'd only had experience with C++ before getting this job, so I only knew cout/cin. And even after 2 years of work on pretty hard embedded code in C, not having screen meant that printing had never come up.
Similarly, many embedded programmers who program in C++ have no experience with the Standard Library, Templates, and sometimes even the "new" keyword, since these are things you often don't use in embedded systems. You can get a false negative if you assume that anyone who doesn't know how to use the Standard Library after 6 years of C++ experience is obviously a bad programmer.
He didn't explain, but the reasoning is that an embedded developer can work for years on projects that dont' have a screen, so there's nothing to print to.
I once found myself in a similar situation. After 2 years of working on an embedded C project (without a screen), I needed to print something. I found out to my horror that I didn't know how to do it - I'd only had experience with C++ before getting this job, so I only knew cout/cin. And even after 2 years of work on pretty hard embedded code in C, not having screen meant that printing had never come up.
Similarly, many embedded programmers who program in C++ have no experience with the Standard Library, Templates, and sometimes even the "new" keyword, since these are things you often don't use in embedded systems. You can get a false negative if you assume that anyone who doesn't know how to use the Standard Library after 6 years of C++ experience is obviously a bad programmer.