Apparently there is no limit to naming conventions for method
-
public void SettingDeviceList_ReAddingAPreviouslyDeletedDevice_MustAddDevicesToRuleDevicesWithIsDeletedFalseAndIsIncludedTrue()
{
return;
}I feel like crying. X|
-
public void SettingDeviceList_ReAddingAPreviouslyDeletedDevice_MustAddDevicesToRuleDevicesWithIsDeletedFalseAndIsIncludedTrue()
{
return;
}I feel like crying. X|
-
public void SettingDeviceList_ReAddingAPreviouslyDeletedDevice_MustAddDevicesToRuleDevicesWithIsDeletedFalseAndIsIncludedTrue()
{
return;
}I feel like crying. X|
Another bright side: you can harmlessly bypass the call :) Function name decoration can also create nice monsters (you can face them when wrapping DLLs), but this is another story.
-
public void SettingDeviceList_ReAddingAPreviouslyDeletedDevice_MustAddDevicesToRuleDevicesWithIsDeletedFalseAndIsIncludedTrue()
{
return;
}I feel like crying. X|
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|
How about this test method: AnalyseSchoolHistoryForConflicts_SchoolHistoryHasStartDateAndEndDateAndIncomingItemStartDateIsInbetween_DatesOverlapWarningAdded() This is a unit test method. It says what it's testing, the scenario and the expected outcome.
-
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.