DEV Community

Discussion on: Philosophy of a Good Developer

Collapse
 
joemaffei profile image
Joe Maffei • Edited

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”.

Collapse
 
murrayvarey profile image
MurrayVarey

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.

Collapse
 
sarthology profile image
Sarthak Sharma

Interesting 🤔