Apparently there is no limit to naming conventions for method
-
Yeah, its like climbing Rapunzel's tower to find out that she is actually a he.
In this case, she is actually a he, and he's an inflatable doll.
Software Zen:
delete this; -
This looks to me like a unit testing attempt, similar to the recommendations in "The Art of Unit Testing" : featureundertest_when_expectation Usually these methods are long, but they are supposed to be read like a sentence.
Make it simple, as simple as possible, but not simpler.
-
public void SettingDeviceList_ReAddingAPreviouslyDeletedDevice_MustAddDevicesToRuleDevicesWithIsDeletedFalseAndIsIncludedTrue()
{
return;
}I feel like crying. X|
You guys have obviously never written any objective C. The following method signature (without defined parameter names) is a legit initializer method from the Apple code base for the NSBitmapImageRep[^][] object. God only knows what some users have made.
initWithBitmapDataPlanes:pixelsWide:pixelsHigh:bitsPerSample:samplesPerPixel:hasAlpha:isPlanar:colorSpaceName:bitmapFormat:bytesPerRow:bitsPerPixel:
-
In this case, she is actually a he, and he's an inflatable doll.
Software Zen:
delete this; -
public void SettingDeviceList_ReAddingAPreviouslyDeletedDevice_MustAddDevicesToRuleDevicesWithIsDeletedFalseAndIsIncludedTrue()
{
return;
}I feel like crying. X|
What is actually so bad about this? The length only? If yes, then WTF? You are kvetching about length? Why? If not, then fill it in here: __________________________
-
What is actually so bad about this? The length only? If yes, then WTF? You are kvetching about length? Why? If not, then fill it in here: __________________________
-
Eh? Unreadable in what sense? I can read quite clearly, as well as understand the intent. Long names are inherently self-documenting. I sincerely do NOT understand your response. To me, tersely abbreviated names are not only unreadable, but quite unnecessary in this day-and-age of auto-completion.
-
public void SettingDeviceList_ReAddingAPreviouslyDeletedDevice_MustAddDevicesToRuleDevicesWithIsDeletedFalseAndIsIncludedTrue()
{
return;
}I feel like crying. X|
I've used support software from a certain hardware manufacturer. I think their software was written by an intern. All of the names are of the form:
#define ACR1_ACR2_ACR3_..._ACRN 0x........
where each
ACR_i_is a three or four letter acronym for a hardware signal or state. Some of the names are well over 100 characters long, and completely unreadable.Software Zen:
delete this; -
Eh? Unreadable in what sense? I can read quite clearly, as well as understand the intent. Long names are inherently self-documenting. I sincerely do NOT understand your response. To me, tersely abbreviated names are not only unreadable, but quite unnecessary in this day-and-age of auto-completion.
-
Eh? Unreadable in what sense? I can read quite clearly, as well as understand the intent. Long names are inherently self-documenting. I sincerely do NOT understand your response. To me, tersely abbreviated names are not only unreadable, but quite unnecessary in this day-and-age of auto-completion.
The same reason that writing a 4 page essay in a comment in the lounge is unreadable. You have to parse a lot of text before you can begin to understand what the purpose is. Just get to the point, which I'm sure can be expressed in fewer than 15 words or however many are in that title.
-
Yeah, its like climbing Rapunzel's tower to find out that she is actually a he.
-
Eh? Unreadable in what sense? I can read quite clearly, as well as understand the intent. Long names are inherently self-documenting. I sincerely do NOT understand your response. To me, tersely abbreviated names are not only unreadable, but quite unnecessary in this day-and-age of auto-completion.
-
You guys have obviously never written any objective C. The following method signature (without defined parameter names) is a legit initializer method from the Apple code base for the NSBitmapImageRep[^][] object. God only knows what some users have made.
initWithBitmapDataPlanes:pixelsWide:pixelsHigh:bitsPerSample:samplesPerPixel:hasAlpha:isPlanar:colorSpaceName:bitmapFormat:bytesPerRow:bitsPerPixel:
-
Eh? Unreadable in what sense? I can read quite clearly, as well as understand the intent. Long names are inherently self-documenting. I sincerely do NOT understand your response. To me, tersely abbreviated names are not only unreadable, but quite unnecessary in this day-and-age of auto-completion.
In college, did you title your essays using the entire contents of the essays, or did you use something shorter? Longer variables take longer for humans to read, they can lead to extra horizontal scrolling (the Devil!), they take longer to type, and they are not necessary.
INSWSAEJETGTMA...
Im_Not_Saying_We_Should_Abbreviate_Excessively_Just_Enough_To_Get_The_Meaning_Across...
// If you want to explain something more, put it in a comment above the variable declaration so it doesn't follow the variable around.
abbreviateAppropriately... -
In college, did you title your essays using the entire contents of the essays, or did you use something shorter? Longer variables take longer for humans to read, they can lead to extra horizontal scrolling (the Devil!), they take longer to type, and they are not necessary.
INSWSAEJETGTMA...
Im_Not_Saying_We_Should_Abbreviate_Excessively_Just_Enough_To_Get_The_Meaning_Across...
// If you want to explain something more, put it in a comment above the variable declaration so it doesn't follow the variable around.
abbreviateAppropriately.../** <summary>That should go here.</summary> */
[Description("Or perhaps here.")]
abbreviateAppropriately...so it does follow the method around and is more localizable.
-
public void SettingDeviceList_ReAddingAPreviouslyDeletedDevice_MustAddDevicesToRuleDevicesWithIsDeletedFalseAndIsIncludedTrue()
{
return;
}I feel like crying. X|
-
public void SettingDeviceList_ReAddingAPreviouslyDeletedDevice_MustAddDevicesToRuleDevicesWithIsDeletedFalseAndIsIncludedTrue()
{
return;
}I feel like crying. X|
I thought I am the naming jerk :laugh:
-
Look on the bright side - it's broken up into easily manageable chunks by _'s Imagine it was not...
-
Nice ans well, but I expect some rcommendation any time now that will tell us to wear feathers on our heads and chant while dancing around the computer.
At least artificial intelligence already is superior to natural stupidity
-
What is actually so bad about this? The length only? If yes, then WTF? You are kvetching about length? Why? If not, then fill it in here: __________________________
SettingDeviceList_ReAddingAPreviouslyDeletedDevice_MustAddDevicesToRuleDevicesWithIsDeletedFalseAndIsIncludedTrueYou genuiely think this is readable? I got bored half way through, though it is 1 am where I am.Michael K Gray wrote:
If not, then fill it in here:
Well in probability this is several methods and attributes:
public void ReAddRequiredDeletedDevice()
{
//OK this if is a punt, but if gives the idea
if(!Device.IsDeleted && Device.IsIncluded)
{
//Add or whatever
}
}public void SetDeviceList()
{
ReAddRequiredDeletedDevice();
return; //Hey the one useful line of code from the OP!
}Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^]