4 ms·

He has it backwards. Choose the developers because they are good, then let them choose the programming languages.

• deleted 16y ago
  [deleted]
• dagw 16y ago
  The problem with that approach is you'll end up with a program written in a dozen different languages and no single person can understand it. I once worked at place that had a, relatively small, code base that contained more or less equal parts tcl, C, Lisp, Visual Basic, C++, Perl and probably something I'm forgetting due to the fact that the programmers got to choose their languages without any sort of supervision. It was no fun at all for anyone to work with.
  • amorphid 16y ago
    Having to support that many languages sounds like a pain. It's also be tough to hire train junior developers who had decent mastery of one language but not several. I'd rather have a junior person really know their stuff in one language than me average in multiple things.
  • Uchikoma 16y ago
    I once worked at a place that had a code base that contained more or less parts in Ruby, Perl, Java and PHP. It was not fun at all to keep enough knowledge in the company over the years to maintain this nightmare.