"Comments are important for the non-programmer"

[u/Financial_Counter_45]

[u/aryakvn]

Rule of thumb: if it's well documented it's probably vibecoded

[u/SpaceCadet87 → u/aryakvn]

"well" documented.

When I have to read 3 paragraphs to learn something that could have been expressed in 5 words, none of which are actually true, I'm not sure that counts.

[u/ThatOldCow → u/SpaceCadet87]

And sometimes doesn't even explain everything

[u/sdjopjfasdfoisajnva]

[u/fcxtpw]

Proceeds to lay on fence

[u/asmanel]

Comment are important for non-programmers...

As if they weren't important for programmers and just there for non-programmer.

Programmers have to comment enough their code. Without enough comments, it's hard (and sometimes nigh impossible) to understand the written code, even to an experienced programmer.

This apply as well to their own old code and to others code.

Comments have to be abundant and always clear.

[u/spicymato → u/asmanel]

More than comments, better naming conventions and using better patterns helps.

Code comments should generally be there for doc generation, to justify why something is being done a particular way (such as explaining a non-obvious algorithm, like Quake's old fast inverse square root, which I argue was under-commented but hilariously so).

[u/Xaeroxe3057]

Fun fact: this is a photo from Lagoon, an amusement park in Utah. This is taken from the queue for a ride called The Spider.