3 ms·

There's nearly always another language to use to get the job done Sure, but in most cases programmers spend most of their time only in one 'part' of the system

by dagw 8y ago

There's nearly always another language to use to get the job done Sure, but in most cases programmers spend most of their time only in one 'part' of the system and only really have to know the language that part of written. In general it doesn't matter if the back end server is written in Lisp, Java or APL, as long as it talks to my part of the system in the way it's supposed to.

danans 8y ago
> in most cases programmers spend most of their time only in one 'part' of the system Perhaps that's a reflection of the structure of the organizations they work in. Anyways, the other cause of multilingualism is switching jobs, projects, or problem spaces. All three of those often involve a language switch.