4 ms·
At my company we're finally trying to write code in English (much to the despair of way more developers than I would have expected), but one serious difficulty
by hadrien01 8y ago
At my company we're finally trying to write code in English (much to the despair of way more developers than I would have expected), but one serious difficulty we've encountered (appart from people that don't know how to write correct sentences...) is translating domain-specific terms. Either it seems like bad translation, or it's not understandable at all.
I don't know what the solution should be in that case? Keep domain-specific terms in French?
- arp242 8y agoI've also ran in to the reverse problem: mixing English and Dutch in confusing ways. For example, a common naming pattern in is `GetFooByID()`, `GetFooByName()`, etc. I think it makes sense to stick to that, but if `Foo` is a non-English word it just gets confusing/inconsistent, especially because in some cases you would translate Foo and other cases you don't. On the other hand, translating domain-specific terms can also be very confusing. For example at my previous position we built a rental contract system that was very specific to the Dutch rental system/laws. We translated everything to English, but a lot of stuff is just funky because it's a specific Dutch term without a real English translation (for example names of specific laws/procedures). My advice is to give up, destroy your code base, and become a sheep herder. You're screwed no matter what.
- wingerlang 8y agoMy bother worked in this situation, they kept the domain specific words in the local language because translating would be difficult.
- j1elo 8y agoI'd say if it's a country-specific thing with domain terms that one would need to learn and know anyway to do the work, even if the programmer was foreigner... then keep those terms without translation. It will be less confusing.