Code is meant to be read by others, and it's a very information-dense medium. So write your code like you'd write a book or an article, *not* like a telegram or a SMS circa 2005. Spell out those variable names. No one-letter variables or weird abbreviations, please.
-
-
I feel like idx works better than i if it's actually a list index! I still use i, but only for anonymous iterations where it only represents a range.
-
Gonna start using this, thanks!
End of conversation
New conversation -
-
-
I'm using "for token_i, token in enumerate(sequence)" as an example. The additional information is really helpful, especially when dealing with nested for-loops. – Even naming standards can be made more explicit, without breaking learned patterns.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
undrstndabl and not anoyying
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Once I had to deal with FORTRAN code without IMPLICIT NONE. I think we have made great strides in readability in the last few decades.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
In case anyone had trouble parsing that last part: "In many cases short variable names can't be interpreted".
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.