61–63 of 63 posts
From https://en.wikipedia.org/wiki/Psychology_of_programming ; 1) Human Technology (online journal, papers) - https://ht.csr-pub.eu/index.php/ht/index 2) Psychology of Programming Interest Group (papers) - https://www.ppig.org/ 3) Cognitive Biases in Software Engineering: A Systematic Mapping Study - https://arxiv.org/abs/1707.03869
From https://en.wikipedia.org/wiki/Psychology_of_programming ; 1) Human Technology (online journal, papers) - https://ht.csr-pub.eu/index.php/ht/index 2) Psychology of Programming Interest Group (papers) - https://www.ppig.org/ 3) Cognitive Biases in Software Engineering: A Systematic Mapping Study - https://arxiv.org/abs/1707.03869
(3) has an exciting title but the methodology is: "we observed 10 (ten) developers ..."
That phrase does not occur in the paper linked to in (3) above (i.e. "Cognitive Biases in Software Engineering: A Systematic Mapping Study") at all.
The Abstract itself states;
One source of software project challenges and failures is the systematic errors introduced by human cognitive biases. Although extensively explored in cognitive psychology, investigations concerning cognitive biases have only recently gained popularity in software engineering research. This paper therefore systematically maps, aggregates and synthesizes the literature on cognitive biases in software engineering to generate a comprehensive body of knowledge, understand state of the art research and provide guidelines for future research and practise. Focusing on bias antecedents, effects and mitigation techniques, we identified 65 articles (published between 1990 and 2016), which investigate 37 cognitive biases. Despite strong and increasing interest, the results reveal a scarcity of research on mitigation techniques and poor theoretical foundations in understanding and interpreting cognitive biases. Although bias-related research has generated many new insights in the software engineering community, specific bias mitigation techniques are still needed for software professionals to overcome the deleterious effects of cognitive biases on their work.
I feel like there could be a lot of value in understanding the psychology of teams and using it to build an environment where they can thrive. However, every person I've worked with who was into these workplace-psychology books started thinking of themselves as expert diagnosticians of other people's psychology. Every personality or problem got mapped back to a scenario from a book they read, even when it wasn't a go…
Doesn't that happen with any first-year psychology or med-student, too? You have some basic knowledge of what could happen, which therefore means that it does happen, right now, here. It normally goes away with more experience and exposure, and yeah, some personal growth.