We have dribbled a lot with this issue, and developers feeling pinned and feeling especially reviewed. Often this is the result of a somewhat less invested developer who does not care or understand enough to write it as good as other team members. We have had days devoted to discuss how feedback is best presented, and it took us (8 devs) a good 3-4 months before we could go back to public, written reviews in gitlab that was received as constructive for the code/product and not personally attacking comments.
That being said, sitting down, discussing what type of feedback and wording is perceiced as persoanlly attacking and having a dialog where the team can suggest less invasive methods. We for example used personal video meets (2-3 peeps) and then wrote down the review comments together as sort of an "agreement" on the merge request. Doing this process i think helped the devs tp understand all the thought behind a review and not just look at the words and read them as personlly attacking.
Btw I was tech lead and did reviews, and I led this intervention, making sure everyone got heard.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
I have never heard of such an action, it sounds like a fantastic idea though, I am forming a team, this could be an area where problems appear, I will keep this in mind as an action.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
We have dribbled a lot with this issue, and developers feeling pinned and feeling especially reviewed. Often this is the result of a somewhat less invested developer who does not care or understand enough to write it as good as other team members. We have had days devoted to discuss how feedback is best presented, and it took us (8 devs) a good 3-4 months before we could go back to public, written reviews in gitlab that was received as constructive for the code/product and not personally attacking comments.
That being said, sitting down, discussing what type of feedback and wording is perceiced as persoanlly attacking and having a dialog where the team can suggest less invasive methods. We for example used personal video meets (2-3 peeps) and then wrote down the review comments together as sort of an "agreement" on the merge request. Doing this process i think helped the devs tp understand all the thought behind a review and not just look at the words and read them as personlly attacking.
Btw I was tech lead and did reviews, and I led this intervention, making sure everyone got heard.
Hope this can help.some teams.out there!
I have never heard of such an action, it sounds like a fantastic idea though, I am forming a team, this could be an area where problems appear, I will keep this in mind as an action.