Egoless programming: Difference between revisions
No edit summary |
Undid revision 359671497 by 76.115.50.244 (talk) |
||
| Line 7: | Line 7: | ||
==Peer reviews of code== |
==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 |
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, collegiate 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=http://books.google.com/books?id=d7BQAAAAMAAJ&pgis=1|page=14|title=Peer Reviews in Software: A Practical Guide|author=Karl Eugene Wiegers|ibn=0201734850|year=2001|publisher=Addison-Wesley}}</ref> |
||
==Rival concepts== |
==Rival concepts== |
||
Revision as of 19:50, 2 May 2010
Egoless programming is a style of computer programming in which personal factors are minimised so that quality may be improved. The cooperative methods suggested are similar to those used by other collective ventures such as Wikipedia.
Origin
The concept was first propounded by Jerry Weinberg in his seminal book, The Psychology of Computer Programming.[1]
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, collegiate way in which personal feelings are put aside. Structured walkthroughs are one way of making such a formal review.[2]
Rival concepts
Egoless programming explicitly minimises constraints of hierarchy and 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.[3]
See also
References
- ^ Gerald M. Weinberg (1971). The Psychology of Computer Programming. Van Nostrand Reinhold.
- ^ Karl Eugene Wiegers (2001). Peer Reviews in Software: A Practical Guide. Addison-Wesley. p. 14.
{{cite book}}: Unknown parameter|ibn=ignored (help) - ^ Penny Grubb, Armstrong A. Takang, Software maintenance: concepts and practice