Language Choice
Yeah, I don't like this article. Idk who would read it lmao. I just sound high and mighty
You are given some problem, and you need to pick a language. These situations are either what you should interview in, what you should use to solve this problem at-hand, and what language to use when creating a new service.
For interviewing, I typically default to Python unless it's explicitly a low-level interview or a language-themed interview. I don't really do low-level programming at work, and the fluff of debating whether unique_ptr, weak_ptr, raw pointer, or more, ends up just getting in the way of an interview. If you are explicitly looking for low level roles like Azure storage, embedded technology, or CUDA programming, you're basically forced into this. Ideally, you only use C/C++ for C++ themed interviews, and not data structure ones. Again, if you're in the middle of implementing a union find you're exposing yourself to the risk of the interviewer just asking you why you aren't using a unique pointer.
Career-wise, unless it's a domain-knowledge specific job, I see jobs that filter on language as a red flag. It means the recruiter or hiring manager doesn't really understand how software engineers function, or they assume your tenure at the company is going to be so short that you don't even have time to learn how to use the equivalent of their python flask library. They could be using it as an indication of the types of problems you work on, but in this case you should also entirely ignore the language they're saying.
I enjoy writing C++, but I think people have a strong tendency to over-value C++ jobs because they appear to be challenging. With C++, you end up taking much longer to develop smaller parts of code. In other words, you have less business-impact than someone using a high-level language. Do you want to have less business impact and get involved in unnecessary problems?
So, in summary, unless the specific domain you already have experience in is oriented around C++, just use Python.