in reply to Re: Revisiting the old clichés of programming languages (natural languages)
in thread Revisiting the old clichés of programming languages

Were I an interviewer I would not like that answer. No matter how much better you know Perl, there are generic valid reasons to write in Python instead that you can give that interviewer:
  1. A personal project to help you learn Python, some Python library, etc. (Note, learning how a framework in another language does something is an excellent way to open your mind to new ways to do it in Perl.)
  2. An existing Python project has a lot of the functionality you need, and extending it looks easier than rewriting it.
  3. The team that will have to support and maintain it are Python developers rather than Perl developers.
  4. A client is willing to pay you to write in Python, and is willing to accept your reduced productivity.
What you're trying to demonstrate with these answers are that you are open to working with others, fitting yourself to an organization's needs, and learning. The answer you gave instead could leave the impression that you have none of those traits.

The only time I would want to leave an interviewer with those types of negative impressions of me is if working with a particular language was so distasteful that I really don't want a job where I have to do that. The only language that I feel that way about is VB. Certainly I don't feel that way about Python. Furthermore Python has some good features that I wish were in Perl. For instance Perl has nothing equivalent to Python's list comprehensions and generators.

  • Comment on Re^2: Revisiting the old clichés of programming languages (natural languages)

Replies are listed 'Best First'.
Re^3: Revisiting the old clichés of programming languages (Python)
by kyle (Abbot) on Jan 26, 2009 at 22:17 UTC

    As it happens, most of what I know about Python comes from three out of four of the motivations you list. I wanted to add a feature to an existing (open source) Python project (maintained by Python programmers, natch), in part because I wanted to learn about the language. I also discussed that in the same interview, just not in answer to that question.

      That's good, and I want to be clear that I'm not accusing you of having the negative traits. I'm just saying that when you give that answer, you don't know how it will be heard. And some interviewers will hear that answer in a very bad way.

      The potential for harm is mitigated a lot if you have already discussed your willingness to work with Python in other circumstances. But if the job they envision is 70% Python and 30% Perl, you've still potentially argued yourself out of a job for a skill that you realistically could come up to speed on well within the usual window of 1-3 months that most people need to become productive.