This is interesting, but I disagree. It's certainly possible to be able to engage in rational discussion about things related to ones own identity.
I am a programmer, and primarily I identify as a C++ and Python programmer. Compared to other languages, for a given problem (unless it's truly massive, where the efficiency/expressiveness gain over the other two is large to offset becoming an expert in it), I am almost certainly going to provide an adequate solution quickest in one of those languages.
But if you say that Python is slow, doesn't do concurrency well, or has trouble scaling to truly large, 100+ programmer codebases, I'll agree with you.
And if you call C++ a large, ugly, language with a ton of ways to really screw yourself, and that is tied to a slow edit/compile/debug cycle, I'll agree with you there too.
Here perhaps maybe enlarging my identity helped, if I was just a Python programmer, I wouldn't see how static typing and a really good code searching system would help getting an anchor on a large, complicated C++ code base. Those static types and non-virtual functions means that yes, I can see every place that this particular function is called in our entire code base without having to dig all that much. And if I was just a C++ programmer, I wouldn't know the bliss that is hacking a 200 line program in Python, and solving some mildy complicated but mostly self contained problem in few hour session, all without the bondage of makefiles, compiles, static typing and seg faults.
I am a programmer, and primarily I identify as a C++ and Python programmer. Compared to other languages, for a given problem (unless it's truly massive, where the efficiency/expressiveness gain over the other two is large to offset becoming an expert in it), I am almost certainly going to provide an adequate solution quickest in one of those languages.
But if you say that Python is slow, doesn't do concurrency well, or has trouble scaling to truly large, 100+ programmer codebases, I'll agree with you.
And if you call C++ a large, ugly, language with a ton of ways to really screw yourself, and that is tied to a slow edit/compile/debug cycle, I'll agree with you there too.
Here perhaps maybe enlarging my identity helped, if I was just a Python programmer, I wouldn't see how static typing and a really good code searching system would help getting an anchor on a large, complicated C++ code base. Those static types and non-virtual functions means that yes, I can see every place that this particular function is called in our entire code base without having to dig all that much. And if I was just a C++ programmer, I wouldn't know the bliss that is hacking a 200 line program in Python, and solving some mildy complicated but mostly self contained problem in few hour session, all without the bondage of makefiles, compiles, static typing and seg faults.