Why can't you guys comment your fucking code?

Re:Why can't you guys comment your fucking code? by Cieplak on Tuesday July 04, 2017 @02:59AM (#14694066)

I hate to disagree but that's fairly clean code. It's not doing anything tricky or exceedingly clever, so the code speaks for itself. They're even polite enough to separate their implementation from their interface, which is rare for projects in dynamic languages. It reads like idiomatic, OO, pep8'd python. Python is basically executable pseudocode as it is, provided the method names and parameters convey the semantics of the code.

https://github.com/facebookresearch/end-to-end-negotiator/bl...

[ Parent | on HN ]

Re:Why can't you guys comment your fucking code? by stubish on Tuesday July 04, 2017 @05:30AM (#14694662)

The code speaks for itself, so there is no way to confirm it works as intended. Because the intention is undocumented.

The code tells what the program does. The comments should state what it is supposed to be doing and why it should do it. When they don't match you have found a bug.

[ Parent | on HN ]

Re:Why can't you guys comment your fucking code? by DigitalJack on Tuesday July 04, 2017 @08:59AM (#14695585)

“Code never lies. Comments sometimes do.”

I forget who that quote is attributed to.

[ Parent | on HN ]

Re:Why can't you guys comment your fucking code? by herbst on Tuesday July 04, 2017 @11:31AM (#14696432)

Pretty sure that is what unit testing is for. No excuse for wasting time on comments

[ Parent | on HN ]