Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Psychology of programming
open-in-new
<h2 id="history">History</h2> <p>The history of psychology of programming dates back to late 1970s and early 1980s, when researchers realized that computational power should not be the only thing to be evaluated in programming tools and technologies, but also the usability from the users.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> In the first Workshop on Empirical Studies of Programmers, <a href="/facts/Ben_Shneiderman/y6JH0pFh">Ben Shneiderman</a> listed several important destinations for researchers. These destinations include refining the use of current languages, improving present and future languages, developing special purpose languages, and improving tools and methods. Two important workshop series have been devoted to psychology of programming in the last two decades: the Workshop on Empirical Studies of Programmers (ESP), based primarily in the US, and the Psychology of Programming Interest Group Workshop (PPIG), having a European character. ESP has a broader scope than pure psychology in programming, and on the other hand, PPIG is more focused in the field of PoP. However, PPIG workshops and the organization PPIG itself is informal in nature, It is group of people who are interested in PoP that comes together and publish their discussions. </p> <h2 id="goals-and-purposes">Goals and purposes</h2> <p>It is desirable to achieve a programming performance such that creating a program meets its specifications, is on schedule, is adaptable for the future and runs efficiently.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> Being able to satisfy all these goals at a low cost is a difficult and common problem in software engineering and project management. By understanding the psychological aspects of computer programming, we can better understand how to achieve a higher programming performance, and to assist programmers to produce better software with less error. </p> <h2 id="research-methods">Research methods</h2> <p>Some methods which one can use to study the psychological aspects of computer programming include <a href="/facts/Introspection/X8rBdaR0">introspection</a>, <a href="/facts/Observation/NTodmzCo">observation</a>, <a href="/facts/Experiment/esltM54f">experiment</a>, and <a href="/facts/Qualitative_research/po7v42yR">qualitative research</a>.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> </p> <h2 id="cognitive-biases">Cognitive biases</h2> <p><a href="/facts/Cognitive_bias/49YKVhmN">Cognitive biases</a> are systematic differences from an optimal way of reasoning about something. Research has suggested there are a number of biases involved in programming.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> <a href="/facts/Anchoring_bias/V793WguQ">Anchoring bias</a> have been identified for <a href="/facts/Cost_estimation_in_software_engineering/f1qohGrr">estimation</a> and the reuse of ideas.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a>: 7 There is an <a href="/facts/Optimism_bias/UTPq1gMQ">optimism bias</a> applies to work being carried out.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a>: 7 <a href="/facts/Availability_bias/BMwkXqxD">Availability bias</a> can cause programmers to use incorrect keywords when searching documentation and not find relevant information and prevent programmers from applying lessons learned from previous projects in an organization.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a>: 7 </p><p><a href="/facts/Confirmation_bias/o5rHY4lP">Confirmation bias</a> can apply to <a href="/facts/Software_testing/VoXzG9Tb">testing</a> leading developers to write test cases that will work for the code rather than those that are likely to fail. It can also apply to searching documentation only for a programmers current hypothesis. Training in <a href="/facts/Logical_reasoning/NwR4hQva">logical reasoning</a> and <a href="/facts/Hypothesis_Testing/yv9RPF6U">hypothesis testing</a> reduced this confirmation bias. <a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a>: 7 </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Cognitive_psychology/GnzIgx2I">Cognitive psychology</a></li> <li><a href="/facts/Human_computer_interaction/EkmIxGCx">Human computer interaction</a></li> <li><a href="/facts/Learning/lehEKRjC">Learning</a></li> <li><a href="/facts/Problem_solving/9cuLz5pH">Problem solving</a></li></ul> <h2 id="external-links">External links</h2> <ul><li><a href="http://www.ppig.org">Psychology of programming web site</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Jorma Sajaniemi. Psychology of Programming: Looking into Programmers’ Heads. Human Technology [Internet]. 2008 May 4–8 [cited 2012 Oct 4]; 4(1): Available from: http://www.humantechnology.jyu.fi/articles/volume4/2008/ge-sajaniemi.pdf <a href="http://www.humantechnology.jyu.fi/articles/volume4/2008/ge-sajaniemi.pdf" target="_blank">http://www.humantechnology.jyu.fi/articles/volume4/2008/ge-sajaniemi.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Weinberg, Gerald M. (1998), The Psychology of Computer Programming (Silver ed.), New York: Dorset House, ISBN 0-932633-42-0 <a href="0-932633-42-0" target="_blank">0-932633-42-0</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Weinberg, Gerald M. (1998), The Psychology of Computer Programming (Silver ed.), New York: Dorset House, ISBN 0-932633-42-0 <a href="0-932633-42-0" target="_blank">0-932633-42-0</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Mohanani, Rahul; Salman, Iflaah; Turhan, Burak; Rodriguez, Pilar; Ralph, Paul (2020-12-01). "Cognitive Biases in Software Engineering: A Systematic Mapping Study". IEEE Transactions on Software Engineering. 46 (12): 1318–1339. arXiv:1707.03869. doi:10.1109/TSE.2018.2877759. ISSN 0098-5589. S2CID 2172676. <a href="https://ieeexplore.ieee.org/document/8506423" target="_blank">https://ieeexplore.ieee.org/document/8506423</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Mohanani, Rahul; Salman, Iflaah; Turhan, Burak; Rodriguez, Pilar; Ralph, Paul (2020-12-01). "Cognitive Biases in Software Engineering: A Systematic Mapping Study". IEEE Transactions on Software Engineering. 46 (12): 1318–1339. arXiv:1707.03869. doi:10.1109/TSE.2018.2877759. ISSN 0098-5589. S2CID 2172676. <a href="https://ieeexplore.ieee.org/document/8506423" target="_blank">https://ieeexplore.ieee.org/document/8506423</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>Mohanani, Rahul; Salman, Iflaah; Turhan, Burak; Rodriguez, Pilar; Ralph, Paul (2020-12-01). "Cognitive Biases in Software Engineering: A Systematic Mapping Study". IEEE Transactions on Software Engineering. 46 (12): 1318–1339. arXiv:1707.03869. doi:10.1109/TSE.2018.2877759. ISSN 0098-5589. S2CID 2172676. <a href="https://ieeexplore.ieee.org/document/8506423" target="_blank">https://ieeexplore.ieee.org/document/8506423</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>Mohanani, Rahul; Salman, Iflaah; Turhan, Burak; Rodriguez, Pilar; Ralph, Paul (2020-12-01). "Cognitive Biases in Software Engineering: A Systematic Mapping Study". IEEE Transactions on Software Engineering. 46 (12): 1318–1339. arXiv:1707.03869. doi:10.1109/TSE.2018.2877759. ISSN 0098-5589. S2CID 2172676. <a href="https://ieeexplore.ieee.org/document/8506423" target="_blank">https://ieeexplore.ieee.org/document/8506423</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>Mohanani, Rahul; Salman, Iflaah; Turhan, Burak; Rodriguez, Pilar; Ralph, Paul (2020-12-01). "Cognitive Biases in Software Engineering: A Systematic Mapping Study". IEEE Transactions on Software Engineering. 46 (12): 1318–1339. arXiv:1707.03869. doi:10.1109/TSE.2018.2877759. ISSN 0098-5589. S2CID 2172676. <a href="https://ieeexplore.ieee.org/document/8506423" target="_blank">https://ieeexplore.ieee.org/document/8506423</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> </ol>