Good computer science canon teaches you that the specifics of the computer language you are using are at best "implementation details" and that if you grasp the key core components of computation (indirection, recursion, modularity, etc.) and are a good "computer scientist," it's just a matter of time before you're up to speed in anything from COBOL to OCaml. If this is true though, it's curious to see how many people have turned language choice into a more heated issue that the Red Sox versus Yankees one and how often it keeps coming up in flames and debates.
At the end of the day, I too would like to believe the theory that we are all just huge brains floating in jars full of jelly wired with electrodes and that external stimuli like syntax, core language constructs, whether there is an explicit compile step, static typing, etc. can just be adapted to by moving a few of the electrodes around. Unfortunately, experience just doesn't bear it out.
Which is why I found Luke Plant's tongue-in-cheek piece about how learning languages like Python and Haskell are making him less of a productive programmer such an entertaining read. For some reason, reading his C# code example made me think of all of those heinous years of programming in Java when I would be left with really ugly constructs like anonymous-inner classes-as-adapters or a horrific introspection API for faking late-binding code (and the fact that early Java heads would talk about how "elegant" these solutions were did not help my confidence at the time either). It's been two years since I've had to do that, and I can honestly say that I will probably never use Java again in any kind of serious project, or C# or any of the other similarly inspired languages (unless forced to under threat of starvation).
The reason is simple: working full-time in Python (and Javascript to some degree) rewires those brain electrodes in a really positive way (if your goal is fast development and deferring design decisions as long as possible which it should be for any web application developer; perhaps not so true for avionics engineers) and it would be both painful and counterproductive to go back at this point. Others have written extensively about this but the basic argument is that with an highly expressive, consistent, low-overhead language, you get a ton more time to think through the real problem. Conversely, another way to put it that is more in tune with my particular circumstances these days is that you need a lot less time to experiment and prototype.
So I feel for you Luke– I think if I had to still be writing the cruft that they've got you coding at work, I would also be less productive, but probably mostly from chewing my fingers down to stubs out of frustration. And to all of you computer science bigots with the "I can program in abacus if I have to" mentality– you know, the guys who say the One True Language is LISP even though the only time they've typed more than two parentheses in a row was when they were dabbling in ASCII art or who talk really fast about Turing-complete languages assuming that there is a 1-to-1 exchange rate between insight and speed of talking– to those guys, I look forward to getting you jobs with some of our competitors.