this post was submitted on 15 Jun 2023
122 points (97.7% liked)
Programming
17488 readers
106 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I totally disagree with a lot of this and encourage you to rethink how you communicate with peers.
Calling something someone made dumb is mean. Believe me, I totally get where you're coming from and wish I could separate the emotional aspect from it but it's just not possible. Humans are emotional beings. We make decisions based on emotions and use logic to explain them. You can't just say something that someone made is dumb and expect it to not hurt their feelings because it "would still be dumb if someone else, even [you], wrote it."
It is possible to critique code respectfully without losing anything. I realize you're likely simplifying for the sake of discussion, but consider these examples, which would you rather be told?
These both convey the same message (the code is wrong and how to solve it) but one is polite. The first one is in the gray area and I choose it for that reason. It may very well be true that it is a mistake that amateurs make but saying someone made and "amateur mistake" can be degrading.
People view rude words about their works as rude works about themselves and any appeal to logic will not change that. Just say what you would say but be more polite about it.