Re:“Just remove the duck” (2013)
by pluma on Tuesday March 03, 2015 @12:44PM
(#9139168)
As a non-native English speaker, I can tell you that this is not only perfectly acceptable but actually a good thing.
Naming is important. Bad function names are a bug in the API, just like any other API bug.
Non-native speakers frequently struggle naming things even more than native speakers, especially when they have to deal with a problem domain for the first time.
Just like any other mistake, bad function names usually aren't intentional -- often quite the opposite. I remember struggling with naming business domain related functions and variables in the first booking system I worked on, especially because the UI wasn't localized into English, so I had no direct reference. Should this class be called Invoice or Bill? Are the terms "netto" and "brutto" commonly used in English as they are in German? What's the proper plural of "index"? And so on.
Having tactful help from a native speaker can be a huge advantage.
Naming is important. Bad function names are a bug in the API, just like any other API bug.
Non-native speakers frequently struggle naming things even more than native speakers, especially when they have to deal with a problem domain for the first time.
Just like any other mistake, bad function names usually aren't intentional -- often quite the opposite. I remember struggling with naming business domain related functions and variables in the first booking system I worked on, especially because the UI wasn't localized into English, so I had no direct reference. Should this class be called Invoice or Bill? Are the terms "netto" and "brutto" commonly used in English as they are in German? What's the proper plural of "index"? And so on.
Having tactful help from a native speaker can be a huge advantage.