2 ms·
I certainly don't. Although I also write Rust now, so I suspect someone will accuse me of having split loyalties or something equally ridiculous. The only cont
by woodruffw 4y ago
I certainly don't. Although I also write Rust now, so I suspect someone will accuse me of having split loyalties or something equally ridiculous.
The only context in which I care about "C/C++" is on resumes, where it's a sign that I need to ask a little more about the person's background.
- pengaru 4y ago> The only context in which I care about "C/C++" is on resumes, where it's a sign that I need to ask a little more about the person's background. Is that because you'd expect anyone actually experienced in either to know better than to lump them together so casually?
- woodruffw 4y agoNot necessarily -- I've interviewed plenty of people where "C/C++" meant "experienced in both, but most work was in C with a small smattering of C++" (or vice versa). In my experience, it breaks roughly between half that and half recent graduates who took one C course and one C++ course.
- BenFrantzDale 4y agoFor me, I see “C/C++” as a sign they see C++ (which I’m looking for experience in) as interchangeable with C. I want people who grok C++’s ability to build powerful abstractions, not people messing around with it as C with polymorphic classes.
- ncmncm 4y agoYes. "C/C++" on a résumé is a red flag. "Next!"
- ncmncm 4y agoIt's a sign of a liar, and you can round-file it without reading any more.
- JonChesterfield 4y agoSo far that on a CV has always meant "can write neither C nor C++"