4 ms·
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
by rhaps0dy 11y ago
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.
- bdavisx 11y agoIf 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.
- marpstar 11y agoWhen 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.
- joelcorrea 11y agoThe 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.
- crimsonalucard 11y agoNever abbreviate is my rule of thumb.
- _asummers 11y agoI 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.