That’s good if you write language-agnostic software and live in cool english low level or web bubble. If you take any local business-logic heavy software that uses a big set of terminology, you may regret that it wasn’t written at least by transliteration (better in native). This may be less of a problem for Latin-derived languages. I met this a lot, and it is a reverse problem of what jansan described about VB. You can read ifs and fors, but have no idea what is happening in the code, because names are completely google-translated with no context and then shortened or abbreviated. I highly doubt that non-native speakers could take jobs like that at all, as it is gibberish even for natives.
That’s what my point is. English is zero-profit for non-natives and hard time for natives in these cases. It could work, if a developer were a perfect english writer, and if english were a clear language of all specific terms in existence. But in reality, both conditions fail miserably in this area. Btw, it’s not a legacy pre-internet problem. In a recent local thread around half of developers couldn’t even translate the “income/expense” pair correctly.
Being able to get worlwide support on language/libraries/etc issues, even if you use native words in your business logic, beats writing "si alors sinon" instead of "if then else".
