How many man years are wasted with western naming convensions?
games.greggman.com
How many man years are wasted with western naming convensions?
1–10 of 64 posts
Re: How many man years are wasted with western naming convensions?
#2much less than by poor spelling
Re: How many man years are wasted with western naming convensions?
#3much less than by poor spelling
Or by having to go and check if something is a constant, a variable or a class. Casing provides metadata about an element.
Re: How many man years are wasted with western naming convensions?
#4Maybe I'm being dense, but I fail to see the point. The code has the exact same sequence of tokens in all cases, just with different names for the constant. The fact that a Ctrl+F doesn't find all related uses seems to be the only argument and it doesn't convince me.
The article does not provide an alternative solution, or a discussion of the upsides of different naming conventions (e.g. knowing that ALL_CAPS is almost surely a compile-time constant). "How many man years are wasted..." - compared to what?
Re: How many man years are wasted with western naming convensions?
#5Isn't the real problem here that people unfamiliar with the Latin alphabet will have to learn the Latin alphabet?
I suppose they could design programming languages using the Chinese alphabet (maybe they already have? I wouldn't know) that use different conventions[0].
[0] Convention is with a 't', by the way.
Re: How many man years are wasted with western naming convensions?
#6I'd dread to think of what naming conventions would look like if they were modeled after Japanese. You can write the same exact word as ひとごみ, 人ごみ, 人込み, 人混み, 人込, or even ヒトゴミ if you're feeling bold.
Re: How many man years are wasted with western naming convensions?
#7> Someone had to translate GL_MAX_TEXTURE_SIZE into mMaxTextureSize.
I fail to see how the fact that the Latin alphabet has upper and lower case is to blame for this. This is more about the coding standards the author has to abide to than anything else.
If your coding standard would require you to name the property MMAXTEXTURESIZE instead of mMaxTextureSize, would there be any less busy work?
Re: How many man years are wasted with western naming convensions?
#8The title seems to imply that this problem does not exist in languages not using Latin scripts. That's not true. Take Japanese for an example, when you have hiragana, katakana, and kanji to express the same idea (and not to mention a kanji typically have more than one way of pronouncing it), the problem is gonna be orders of magnitude more complex.
Re: How many man years are wasted with western naming convensions?
#9I agree to some extent. I often trip myself up with filename and fileName (which is right?)
And then there is the hyphen in CSS for example background-color which in js is backgroundColor. (Colour spelt wrong to me in both cases!)
Re: How many man years are wasted with western naming convensions?
#10If this is really a major pain point in some project, there are probably solutions - macros, reflection, code generation, custom build steps and probably more. Or just change your naming convention.