15

Developers who think using cryptic variable names (like acronyms) is better than long descriptive variable names.....but then feel the need to document/comment the variable name rather than just naming the variable properly in be first place.

// Current CGRect to draw into
let ccgrd = self.currentCGRect()

Instead of just

let currentRectForDrawing = self.currentCGRect()

Comments
  • 2
    @NullPointer Totally agree. There a few edge cases where comments might be necessary (complex or exceptional algorithm) but most of the time the code should read like English and I it doesn't decompose it further so you have more functions and variable names that explain what's going on.
  • 2
    I have a different point of view on this. I am a developer from the stone age of course (1988 onwards)
    We had limits on variable name lengths so cryptic was very possible.
    I don't use vowels for e.g.
  • 0
    YES! I had to decode someone's bullshit variables for an intricate calculation yesterday 🙄
  • 0
    It depends on the size of the scope. For two lines, 's' is much better in this specific case.
Add Comment