Egoless programming: Difference between revisions

Revision as of 18:48, 19 October 2016

Revision as of 02:48, 30 October 2016

Line 3:

== Origin ==

The concept was first propounded by [[Gerald M. Weinberg]] in his seminal book of 1971, ''The Psychology of Computer Programming''.<ref>{{cite book | url=httphttps://books.google.co.uk/books?id=76dIAAAAMAAJ&pgis=1 | title=The Psychology of Computer Programming | publisher=Van Nostrand Reinhold | year=1971 | last=Weinberg | first=Gerald M.}}</ref>

==Peer reviews of code==

To ensure quality, reviews of code by other programmers are made. The concept of ''egoless programming'' emphasises that such reviews should be made in a friendly, collegial way in which personal feelings are put aside. [[Software walkthrough|Structured walkthrough]]s are one way of making such a formal review.<ref>{{cite book | url=httphttps://books.google.com/books?id=d7BQAAAAMAAJ&pgis=1 | title=Peer Reviews in Software: A Practical Guide | publisher=Addison-Wesley | year=2001 | page=14 | isbn= 978-0-201-73485-0 | last=Wiegers | first=Karl Eugene}}</ref>

==Strengths==

Line 22:

==Rival concepts==

Egoless programming explicitly minimizes constraints of [[hierarchy]] and [[Social status|status]] so as to enable the free exchange of ideas and improvements. It may be contrasted with the [[chief programmer team]] concept which emphasises specialisation and leadership in teams so that they work in a more disciplined way.<ref>{{Citation | url=httphttps://books.google.com/books?id=ge8o_VkAsiYC&pg=PA210 | title=Software maintenance: concepts and practice | publisher=World Scientific | year=2003 | isbn=978-981-238-426-3 | last1=Grubb | first1=Penny | last2=Takang | first2=Armstrong A.}}</ref>

==See also==