this post was submitted on 26 Nov 2023
711 points (89.3% liked)

Programmer Humor

19623 readers
20 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 1 year ago (3 children)

Code should be self documenting.

[–] JohnDClay 19 points 1 year ago (1 children)

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

[–] [email protected] 8 points 1 year ago

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

[–] [email protected] 10 points 1 year 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.

[–] [email protected] 1 points 1 year ago (1 children)
[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

In a vacuum, sure. On a real project of substantial size with more than one programmer, I'm afraid it quickly becomes a "cannot"