I found this one interesting. The authors note that often, developers avoid code reviews, and engage in a lot of unproductive behavior around them. They claim that a pretty simple one-session cognitive-behavioral intervention can dramatically change that.
Anyway, the longer I work in this field the more I see psychology as the dominant factor in team productivity. Assuming the job is doable, and you’ve hired good people, and the team has adequate control over their own work, that’s what’s left. You might argue that tool use or team practices are more important, but what stops you from adopting them or using them correctly? What stops you from learning from your mistakes? Usually something about your group psychology.
Comments
I haven’t read this book, but I noticed the author makes much of their empirical research available with a CC license.
https://catharsisinsight.com/ , scroll way down to “Developers deserve science.”
I found this one interesting. The authors note that often, developers avoid code reviews, and engage in a lot of unproductive behavior around them. They claim that a pretty simple one-session cognitive-behavioral intervention can dramatically change that.
https://link.springer.com/article/10.1007/s10664-024-10550-9
Anyway, the longer I work in this field the more I see psychology as the dominant factor in team productivity. Assuming the job is doable, and you’ve hired good people, and the team has adequate control over their own work, that’s what’s left. You might argue that tool use or team practices are more important, but what stops you from adopting them or using them correctly? What stops you from learning from your mistakes? Usually something about your group psychology.