I've been writing high-performance C++ since the late '80s, and C a few years before that. I've got three choices; I can earn crap-tastic barely breaking six figures TC writing C++ for a run-of-the-mill application with reasonable work/life balance, or I can write C++ for a fintech earning $400k TC where I'm regularly pulling 70+ hour weeks and abused. Or I can get both bad pay and bad WLB making video games. Alternatively I can go earn $300k TC writing Python with occasional dips into C++ for extra juice with good WLB and my weekends off. Let me think about that.
There's also big, legacy C++ code bases with their own idiomatic way of doing things and every faddish poor practice you can imagine from the past 40 years that'll make you curl up in a ball and cry when you face them.
That's my recipe now, after decades with C++ continuously looking to dump it, the moment I find something better. Dipping into C++ is mostly a backup plan: Numba, Numpy, various GPU targeting tools make it rarely necessary.
There's also big, legacy C++ code bases with their own idiomatic way of doing things and every faddish poor practice you can imagine from the past 40 years that'll make you curl up in a ball and cry when you face them.