Challenge Yourself

  • Yep, the comments should be fairly a high-level description of the coder's intent.

    If the two don't match then the reviewer has to ask questions...

    There is no problem so great that it can not be solved by caffeine and chocolate.
  • In longer procs/scripts I'll add "section breaks", sort of very high-level pseudo-code, to help me quickly identify what a section of code does (or is meant to do). I find that really helpful if/when I have to revisit something months after I last looked at it.

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply