|
|
|
|
|
|
by jamwil
21 days ago
|
|
|
The point of group projects is not to make the best project, it’s to learn to navigate working with other people and all the messiness that entails. Soft skill development and the slackers are a feature not a bug. Doing group projects solo completely defeats the point of the exercise—I’m surprised you got approval from any profs for that. |
|
|
Yes, learning to navigate working with other people is important. But why are you learning that? Because you will need that in work place.
You know what is there in workplace that is not present in varsity project?
Accountability: If someone is not doing their job, you can complain to the manager/boss. There is none in group project.
Authority: In varsity project, everyone is equal. I have no authority over others, even when I have much more experience/know-how. Telling prof one guy is slacking doesn't get much done.
Right to Choose: In work env, if I am highly skilled, I have the option to choose the place I work and thereby increasing the chance of like-minded like-skilled peers. In varsity project, I can get paired with a dumbass and have to bring myself to lowest common denominator. Sorry, I don't (have to) work with idiots in an equal setting. There's a reason that guy is doing some unrelated bank managerial job for $1k/month and I buy $1k worth of collectible items per month without blinking an eye.
If a varsity project is setup in a work env way where I get to interview who joins my team and have the right to fire them if they don't get their shit done, then I'm happy to do group project. Similarly, I'm happy to go thru the same process to join another person's team (if I consider them better).
PS: I did 2 group projects with a friend before that incident and we had zero issues with anything. Simply because we did the work and our skill levels were similar. He's working as Principle Engineer at Oracle now and it is no surprise.