A large part of why I was hired for my current position is that I can explain why returning by move pessimizes NRVO and why an emplace taking a pr-value of the type it's constructing does nothing useful, and I know how to optimize type erasing templates and which compilers provide which opportunities with which attributes and intrinsics, because I read about C++ every day for years. I taught some of my interviewers a little bit about C++ they didn't know before. There were already people on this team with VASTLY greater experience than me overall, but every team needs a certain amount of language expertise to deliver the highest quality software they can. Someone needs to know it, and language esoterica is not something you just pick up without a specific interest in it.
Do you work on high performance/latency sensitive software? That makes total sense in that space, but I also have seen folks obsessing over performance details for contexts where it really doesn’t doesn’t matter at all.
They have a point, the knowledge of C++ compiler intricacies is definitely very valuable, but it can hardly be described merely as programming language knowledge and be compared to, say, Python knowledge.
Yes I am working on tools (some of) which have real time deadlines, albeit not the very strictest ones. We're currently operating around the video game definition of "real time" (and video games are a potential use case), so it's not a problem space where you can't be fast enough and users will always ask for more.
Yeah, but hyperspecializing can be a trap early in your career, or in a weak market. It's perfect when they do look for it, vut I've sadly only had an interview where that would have been nice once in this current (overlong) job hunt.
