this post was submitted on 29 Mar 2025
43 points (77.2% liked)
Programming
19837 readers
651 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yes, being indirect. Instead of saying: 'you did a bad job', say 'here are things you can improve for next time'.
On is confrontational and problematic, the other diplomatic and constructive.
You don't seem to understand what "direct" means.
"You did a bad job" is a subjective value statement that communicates nothing of value. It's direct, but also useless. The problem is not in the directness.
Providing immediate examples of improvements is also direct; the difference is that it's constructive, and helps guide the junior engineer.
One is direct, and the other is not. And you're right, one is not constructive, and the other is, that's not coincidence.
What 'immediate' even means in this context I don't know.
I just didn't want to have to say "direct" again.