this post was submitted on 14 Mar 2025
575 points (99.3% liked)
Programmer Humor
21487 readers
1619 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The only moment you write comments is when you are doing something extremely weird for a specific reason that will not be immediately obvious and you want to warn the person doing a refactor in the future. In any other case, writing self documenting code is the way. If you are unable to do that, then your code needs to be rewrtitten.
Self documenting code is a myth as what's self documenting to one person is not to the next. Code comments and process/workflow documentation is needed for a healthy codebase.
Lmao. Sure buddy.
♫tale as old as time♫ ♫opinions that are mine♫
Not really an opinion when most companies run on self documenting code since time immemorial.
Try handing over your "self documenting code" to a junior dev who doesn't know the language it's written in and see how far they get with it.
Now hand that exact same codebase with comments to the same junior dev, and I guarantee you they'll get further than without the comments.
I have given well documented code to plenty of juniors, it comes with being a senior dev / techlead. And it was perfectly understood. Maybe you simply don't write self documenting code.
Lmao. Sure buddy.