Yes, I tend to do that, and thankfully some of my colleagues do too. Clever but readable solutions, following good and relevant practices, clear documentation, making a good MR description that makes it easier to review, and more.

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

That's great to hear. It's thankfully becoming more common in general, and we can all do our part in spreading these practices.

I tended to actively evangelize for it when I was managing coders or teams. Unfortunately it's still not all that uncommon for coders to be downright offensive when giving feedback, like not necessrily quite Linus-level rants but things like "this is idiotic, this is stupid, that's shit, why would you do that" etc etc. The usual explanation I've gotten is that they're just being "honest" and saying what they think, and it's not their problem if the reviewee (is that even a word‽ I can't English today) gets offended. Some even get all huffy about it, like "oh we're just supposed to coddle them and never say anything negative so their little feefees don't get hurt?" And I mean, yeah, getting honest feedback definitely a good way to learn, but it's not like the only way to point out errors or problems is to be a cunt about it.