916

submitted 1 year ago by alphacyberranger@lemmy.world to c/programmer_humor@programming.dev

42 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] NotAnonymousAtAll@feddit.de 3 points 1 year ago* (last edited 1 year ago)

it’s really useful to comment functions/methods, because otherwise you never know if something’s a bug or a non-obvious feature. Comments act as a parity check to the code, since they tell you what the dev who wrote the code wanted the code to do.

Unit tests should be the parity check for other code. Those don't get outdated with the next refactoring where someone didn't remember to also adjust all the comments.

Also, everone thinks they write good, clean and obvious code. Hardly anyone purpously writes bad, hacky code. Yet if you look at code you wrote a year ago, or code someone else on your team wrote, it’s full of non-obvious hacks. That means, people constantly misjudge the obviousnes of their code. Comments should be put on anything that could maybe be non-obvious.

Why would people be better at judging if something needs a comment than at judging if something needs a better name or refactoring? Asking people to skip that judgement step and comment everything just gives you a bunch of useless boilerplate comments. That trains everyone reading that codebase to ignore comments because they are almost always useless anyway.

putting documentation of the code anywhere else than in a comment (e.g. Confluence) is a total waste of time

At least this we can 100 % agree on. Documentation should be as close as possible to the code. (I just think most of the time that place is in the name of things, not in an actual comment.)

[-] squaresinger@feddit.de 1 points 1 year ago* (last edited 1 year ago)

You can't be too obvious when writing code. Good names, good code structure, unit tests and comments are not mutually exclusive. And comments are the cheapest part of all of that. Commenting what a method does takes a fraction of the time that good code structure or unit tests take, so adding a comment is rarely not worth the effort.

Why would people be better at judging if something needs a comment than at judging if something needs a better name or refactoring? Asking people to skip that judgement step and comment everything just gives you a bunch of useless boilerplate comments. That trains everyone reading that codebase to ignore comments because they are almost always useless anyway.

Again, who is asking them to skip judgement? I am saying, do comments additionally.

And forcing programmers to do anything they don't understand or are against will always result in useless results. I've seen enough unit tests that don't actually test what the tested code does. I've seen nonsense comments. I've seen naming that "follows" the guideline but is totally useless or even wrong. I have even seen code that was implemented in spite and where the code superficially checks all the boxes but is totally terrible once you peek beyond that. Same goes for the whole process. If a programmer doesn't care for code reviews, you get nothing by forcing the programmer to do them.

Does this mean all of these things are useless, just because programmers can purpously sabotage them and find loopholes that fit the guidelines? I don't think so.

At least this we can 100 % agree on. Documentation should be as close as possible to the code. (I just think most of the time that place is in the name of things, not in an actual comment.)

If you can fit all the information about what something does plus all the specifics, edge cases, non-obvious things and the reason why this specific approach was taken in maximum 4 words, then yes. Otherwise comments are the way to go.

Having no documentation is fine for a small project with one dev that will get tossed in a year. But if you are making something that will actually be used for longer, than it's not ok.

[-] Von_Broheim@programming.dev 0 points 1 year ago

If you're writing an explanation of what your code does then, ding ding, you're writing code. If your code has so many side effects and garbage in it that it's incomprehensible without an explanation then it's shit code and I doubt you'd be able to write a comment that explains it that is not equally as shit as the code. Commenting on how shit code works cannot be trusted because the commenter has already proved they're shit at the job by creating that shit code.

Best you can hope for is the comment contains a reason as to why the code is shit.