1

Code comments are good and all, but there's a time and a place for them. They're more or less an opinionated free-form version of what code is doing.

In a library, they're good for documentation. However in a platform, it makes less sense. Especially one which is changing at quite a fast rate (though it has matured in recent months).

Dont get me wrong, we aren't doing wades of horrible, unintelligible code. We need to be sure of what happens when we call a function, so we make sure the signature is always correct.

def do_good_things(puppies): # "good things" is opinionated. Say what you're doing
"""give treats to puppies""" # doc string is wrong
pet(puppies)

Comments
  • 3
    Ive always believed well written code can be absolutely clear as to its purpose without needing comments. I do agree that there is a place for them though, IMO they can be useful for providing context, like why was this code added here, or why is it done this particular way.
  • 1
    @CrashOverride I couldn't agree more.
  • 3
    Better too many comments than too few. How many times has someone written what they thought was "self-documenting" code at the time, just to have to spend hours dissecting the logic the next time they had to dig into it?
  • -1
    You can see the best fun forever to access in to latest euchre online free most people have to visit here https://myeuchre.com for best playing this game and create the high score forever thanks.
  • 0
Add Comment