News for hackers. Stuff that matters.
Re:Choosing good names by rhaps0dy on Sunday June 28, 2015 @10:52AM (#9793720)
I guess the verbosity of the method's name is actually good in this case? Since it makes the function so much clearer.

I am never sure how much to abbreviate a name, but I guess if it's not going to be used much it can be long without problems.

Re:Choosing good names by bdavisx on Sunday June 28, 2015 @11:24AM (#9793830)
If you're using a modern IDE, you shouldn't have to ever type the name out after the first time. I almost never abbreviate anything.
Re:Choosing good names by marpstar on Sunday June 28, 2015 @11:34AM (#9793867)
When I first started using Objective-C, I noticed how verbose the signatures were when passing messages, but really liked how it read when you were scanning the source.

After that, I stopped giving a shit about how long my identifier names are and just make sure they explain in a direct (but concise!) way what that method does or what that variable is.

Re:Choosing good names by joelcorrea on Sunday June 28, 2015 @11:32AM (#9793863)
The verbosity itself shouldn't be a problem, if it someway helps to understand the class / method meaning. But, on the other hand redundancy can be a problem in my opinion, specially considering there is always a context where your code lives.
Re:Choosing good names by crimsonalucard on Sunday June 28, 2015 @12:03PM (#9793967)
Never abbreviate is my rule of thumb.
Re:Choosing good names by _asummers on Sunday June 28, 2015 @02:46PM (#9794558)
I pushed about 6 PRs last week that did nothing but eliminate abbreviations. It was such a minor thing but made me feel so much better. A corollary to your rule is "don't make me think" when reading code. A reader should never have to stop to understand what code is doing, it should be clear. Abbreviations only buy you bytes in the source code at the expense of readability.