Egoless programming: Difference between revisions

Revision as of 00:08, 9 November 2024

Latest revision as of 04:56, 26 March 2025

(2 intermediate revisions by the same user not shown)

Line 9:

==Strengths==

* Works best for complex tasks. ('difficult' used in <ref name="mantei1981"/>)

* Open communication channels allow information to flow freely to team members

* Greater conformity that helps in consistent documentation

Line 19:

* Risky shift phenomenon{{snd}} Programmers attempt riskier solutions to solve a software problem.<ref name="mantei1981">{{cite journal | url=http://sunnyday.mit.edu/16.355/mantei-teams.pdf | title=The Effect of Programming Team Structures on Programming Tasks | last=Mantei | journal=Communications of the ACM |date=March 1981 | volume=24 | issue=3 | pages=106–113 | first=Marilyn | doi=10.1145/358568.358571| s2cid=207907944 }}</ref>

* Simple tasks are made more difficult by open communication channels.{{Clarify|date=February 2020}}{{citation needed|date=June 2014}}

Note: The single paper cited <ref name="mantei1981"/> for 'Strengths & Weaknesses' is from 1981 and says in its conclusions:

<blockquote>Most of the research on group problem-solving behavior was conducted in a laboratory setting with students and tasks of short duration.</blockquote>

<blockquote>None of these task/structure recommendations have been tested in a software development environment.</blockquote>

==Rival concepts==