As a non-native English speaker, I can tell you that this is not only perfectly acceptable but actually a good thing.
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.
Posted by pluma on Mar 3, 2015, 5:44 PM
Tags
Related issues
- Previously you had a few choices, go with: 1.
- Some impressions: I am interested, the single payment is a big plus.
- Well the biggest problem seems to be that the billing from the health provider doesn't sync up with insurance.
- One possible solution is cognitive screening - the use of tests such as the Wonderlic, SAT/ACT, or Wechsler to find prospective empl...
- Names and addresses are extremely difficult to verify as spelling, abbreviations, etc.
- >Lifes are at stake there.
Raise real-world problems, find people facing the same issue, and discuss solutions.7,500 issues0 comments
ux (FinTech)
Previously you had a few choices, go with: 1.
Some impressions: I am interested, the single payment is a big plus.
Well the biggest problem seems to be that the billing from the health provider doesn't sync up with insurance.
One possible solution is cognitive screening - the use of tests such as the Wonderlic, SAT/ACT, or Wechsler to find prospective empl...
Names and addresses are extremely difficult to verify as spelling, abbreviations, etc.
>Lifes are at stake there.
As a non-native English speaker, I can tell you that this is not only perfectly acceptable but actually a good thing.
As a non-native English speaker, I can tell you that this is not only perfectly acceptable but actually a good thing.
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.
Comments (0)
No comments yet. Start the discussion.