How bad programmers comment their code. Good programmers don't comment at all and let the code speak for itself, leaving commenting to some obscure and arcane implementation the coder left in after a week long binge on caffeine and gummy bears.

[–] menas@lemmy.wtf 7 points 4 months ago

Both is good

[–] magic_lobster_party@kbin.run 6 points 4 months ago* (last edited 4 months ago) (1 children)

This is the truth. In my experience, the people who often writes comments are also writing the most incomprehensible code.

Comments are frequently getting outdated as well, so they’re not in great help understanding the code either.

[–] CodexArcanum@lemmy.world 4 points 4 months ago

I was rewriting some old code of mine and ended up stripping out the comments. I kept reading them instead of the code, which I had been changing, and they were irrelevant. (I added new comments back in, though a big reason to rewrite was to make the code more self-explanatory.)

load more comments (6 replies)

[–] isVeryLoud@lemmy.ca 5 points 4 months ago (2 children)

Dankpods screen cap?

[–] Andromxda@lemmy.dbzer0.com 3 points 4 months ago

I don't know. Anyway, DankPods is awesome, there's a great Lemmy community dedicated to his channel: !dingusland@suppo.fi

load more comments (1 replies)

[–] navi@lemmy.tespia.org 5 points 4 months ago (1 children)

A real comment in our junior year game engine codebase.

load more comments (1 replies)

[–] zerofk@lemm.ee 3 points 4 months ago* (last edited 4 months ago)

Our code base is filled with “//constructor”, “//destructor”, “//assignment”, or the ever enlightening “Foo GetFoo(); // GetFoo”.

This is not what they mean by self-documenting code.

[–] fnmain@programming.dev 3 points 4 months ago

Fs.?g??yy V>

load more comments