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".
wruza|6 years ago
palunon|6 years ago
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".