This is a big question. I'm part of a team that is translating the software- and data-carpentry lessons into Spanish and other languages. I'm Spanish and code in English since a very long time, as probably almost everyone who is a member of this community[1]. However, I still think the translation of that material is very important. Many have asked us why to "waste" our time with such translations, suggesting, as many of the people commenting here, that "real" code should be written in English. These courses are aimed at young researchers, normally when they are starting their PhD. If we can do anything to ease their path to get used to the tools that will make their life easier while producing a more sustainable software that helps to open science and replicability, then why wait till they learn English, or why to enforce them to learn the hard way the tools while they don't know English?
I would prefer to read and work with a code in Finnish that's readable than having something bad in English. The problem becomes when there is no consistency and a mix of languages, then you don't know whether the abbreviations used by the previous developer are in one or the other.
[1] Maybe you would get a very different result if you survey this on non-English universities and/or companies.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a big question. I'm part of a team that is translating the software- and data-carpentry lessons into Spanish and other languages. I'm Spanish and code in English since a very long time, as probably almost everyone who is a member of this community[1]. However, I still think the translation of that material is very important. Many have asked us why to "waste" our time with such translations, suggesting, as many of the people commenting here, that "real" code should be written in English. These courses are aimed at young researchers, normally when they are starting their PhD. If we can do anything to ease their path to get used to the tools that will make their life easier while producing a more sustainable software that helps to open science and replicability, then why wait till they learn English, or why to enforce them to learn the hard way the tools while they don't know English?
I would prefer to read and work with a code in Finnish that's readable than having something bad in English. The problem becomes when there is no consistency and a mix of languages, then you don't know whether the abbreviations used by the previous developer are in one or the other.
[1] Maybe you would get a very different result if you survey this on non-English universities and/or companies.