100% agree. To put a positive spin on it: Accept collective responsibility. (I admit it's not as catchy.) It's awesome to feel that your team has your back, and you theirs. I can't imagine collaboration and open discussion happening any other way!
Just to add: collective responsibility is not easy. It takes constant work from everyone. It requires you to stay empathetic towards others feelings. Make the wrong seemingly-innocent comment, and you might have played The Blame Game without realising. This happens (we're only human), but you have to fix things before the trust is gone.
I recommend using a tool like Todo Plus
Great tip -- I'll look into this. I often come across TODOs, shake my fist at it not being done ... and then realise I put it there.
One of the teams I’ve worked with used to blame most code blunders on a long gone developer by calling it “___ code” (insert dev’s name in the blank). git blame often revealed some of us were actually the culprits. We started calling it “us code” because, even though it may have originally been written by another developer, we all looked at and touched that code every day, and did nothing to fix it.
We also encourage devs to turn off VSCode extensions that continuously show git blame output, as they can encourage a silent animosity amongst developers. Once it’s been reviewed, merged and tested, it’s all “us code”.
Exactly! Everyone owns the code. Collective responsibility is a wonderful thing -- literally speaking, it means that everyone has the ability to respond. It also means less scowling at other developers.
That's an interesting point about git blame. I think the term itself is unhelpful. Why does it have to be blame? Sure, it probably started out as a joke, and I chuckled first time round ... but still it sets the tone. Maybe it should be changed to thank. Or hug. Or compadre.
100% agree. To put a positive spin on it: Accept collective responsibility. (I admit it's not as catchy.) It's awesome to feel that your team has your back, and you theirs. I can't imagine collaboration and open discussion happening any other way!
Just to add: collective responsibility is not easy. It takes constant work from everyone. It requires you to stay empathetic towards others feelings. Make the wrong seemingly-innocent comment, and you might have played The Blame Game without realising. This happens (we're only human), but you have to fix things before the trust is gone.
Great tip -- I'll look into this. I often come across TODOs, shake my fist at it not being done ... and then realise I put it there.
Thanks Sarthak!
One of the teams I’ve worked with used to blame most code blunders on a long gone developer by calling it “___ code” (insert dev’s name in the blank).
git blameoften revealed some of us were actually the culprits. We started calling it “us code” because, even though it may have originally been written by another developer, we all looked at and touched that code every day, and did nothing to fix it.We also encourage devs to turn off VSCode extensions that continuously show
git blameoutput, as they can encourage a silent animosity amongst developers. Once it’s been reviewed, merged and tested, it’s all “us code”.Exactly! Everyone owns the code. Collective responsibility is a wonderful thing -- literally speaking, it means that everyone has the ability to respond. It also means less scowling at other developers.
That's an interesting point about git blame. I think the term itself is unhelpful. Why does it have to be blame? Sure, it probably started out as a joke, and I chuckled first time round ... but still it sets the tone. Maybe it should be changed to thank. Or hug. Or compadre.
Interesting 🤔