I used to say this as well, as someone who has done C# (5yrs), Perl(2yrs), and Python(5yrs) work. But the truth is that there is a training/ramp-up period durin

I used to say this as well, as someone who has done C# (5yrs), Perl(2yrs), and Python(5yrs) work. But the truth is that there is a training/ramp-up period during that learning period. When I made the switch from C# to Python it probably took me a year or two before I became as good at Python as I was at C#. This is also true for a lot of the developers I currently work with who are using Python for the first time. There is something to be said about being a master of a language, libraries, and tooling around a certain platform and getting there isn't a quick 1-2 week crash course in the language. Sure you can figure out the syntax and make things work, but if you are truly an expert in 1 language, you wont be comparable in another for at least a year while you use the language and learn the ins-and-outs. People never ask me language questions at work, "how do I do a for loop", but I get daily questions on how virtualenvs work, python packaging, and what libraries to use.