Comment on Bill is a pro grammer

wit@lemmy.world ⁨10⁩ ⁨months⁩ ago

• JohnDClay@sh.itjust.works ⁨10⁩ ⁨months⁩ ago

  But you should also comment it, things obvious to you aren’t obvious to even future you.

  source

  • gornius@lemmy.world ⁨10⁩ ⁨months⁩ ago

    General rule of thumb: Comments say why is it here, not what it does. Code itself should describe what it does.

    source
• Sylvartas@lemmy.world ⁨10⁩ ⁨months⁩ ago

  But then you write code in the real world and find out that you have to write some ass backwards code every other day because of deadlines, backwards compatibility or whatever, and suddenly you realize that despite your best efforts, code cannot always be self documenting.

  Source: me.

  source
• executivechimp@discuss.tchncs.de ⁨10⁩ ⁨months⁩ ago

  should

  source

  • Sylvartas@lemmy.world ⁨10⁩ ⁨months⁩ ago

    In a vacuum, sure. On a real project of substantial size with more than one programmer, I’m afraid it’s a “cannot”

    source