@stratos said:
mmm projects, the best team work in school projects is where your group agree's they suck and the person who can code the best, writes the code. someone else writes the documentation and the guy who sucks at everything but is still in school because he can smooth talk the teachers, defends the project.
If you have a fourth guy, he sabotages the projects from the other groups. Since in most cases your grade will depend on the average quality of turned in projects.
This is true genius! In fact, I believe it works very well in the *real* world too. Between school and work, I have played at least two of the roles in this pattern.
The same pattern can be applied in both school and work in various situations. Even if all three developers can agree that their skills are equivilent in any of the roles, but each has outside constraints (such as other deadlines, planned hangovers, etc), then they can choose to work functionaly disjointly.