3 ms·

> Group projects and emphasizing socialization is a crutch that incompetent teachers use to force their intelligent students to do their job for them. I find t

> Group projects and emphasizing socialization is a crutch that incompetent teachers use to force their intelligent students to do their job for them. I find the opposite true in my career. Business is 95% about how you interact with others; whether that is teaching, listening to, meeting with, understanding morale, etc. Let's look at Agile, socialization is at the key, people over processes, scrum meetings every morning looking for who needs help and who can help, sprint meetings with product managers selling ideas to engineers and engineers discussing how it will be solved, retrospectives where everybody tries to figure out what went right/wrong and what to do better. Then there is pair programming, which is the definition of a group project.

j_s 11y ago
There are often stark contrasts between the idealistic academic approach and the practicalities of the 'real-world' career!
relkor 11y ago
The difference in your Agile and pair programming examples is that those interactions are fundamentally between people with similar abilities. In business, the teaching, listening, and understanding are communication between people with similar baud rates. My impression is that you may be projecting your experiences with groups of competent engineers -- who all passed a rigorous screening process and years of performance reviews -- onto the behavior of children drawn at random from the entire population. Group projects are a tool to adjust the average performance, without any effort on the teacher's part. The effect is more insidious than a simple numerical average would suggest because group projects introduce a time differential. Consider people as an op-amp. Their internal drive to produce a given quality is the reference voltage. What output the currently have (the progess towards the objective) is the input. When you put top performers in a group to pull up the slackers, the feedback gain of that system is artificially reduced. The good students want a certain level of quality, so they will work even harder to try an bring the quality (input signal) up to their standards. Depending on how bad the slackers are, the good student may even reach saturation, running out of hours in the day to compensate for the incompetence of others. The incompetent teachers intuitively understand this effect. They are not fostering some kind of social nirvana, they are transferring the workload of pulling up the class average onto the bright kids. The bright kid ends up spending twice, three times as long on the group assignment, and that effort gets averaged out to the other group members' grades. The cost to top performers is all that time they could have been improving, moving forward, was stuck doing large amounts of low skill work.
megaman22 11y ago
All of these things you are describing are a good way to waste large amounts of time without getting anything worthwhile done. The 5% where you are not interacting with others is the tiny sliver of time you are afforded to actually produce the product that the rest of the business is built on. With the correct group of people, all of this feel-good communication can be replaced by a handful of people that know what they are doing, keeping an online task board updated and communicating primarily asynchronously by email, or if absolutely necessary, synchronously by IM. Pair programming is a great way to make two people half as productive as either would have been working alone.

j_s 11y ago

There are often stark contrasts between the idealistic academic approach and the practicalities of the 'real-world' career!

relkor 11y ago

The difference in your Agile and pair programming examples is that those interactions are fundamentally between people with similar abilities. In business, the teaching, listening, and understanding are communication between people with similar baud rates. My impression is that you may be projecting your experiences with groups of competent engineers -- who all passed a rigorous screening process and years of performance reviews -- onto the behavior of children drawn at random from the entire population. Group projects are a tool to adjust the average performance, without any effort on the teacher's part. The effect is more insidious than a simple numerical average would suggest because group projects introduce a time differential. Consider people as an op-amp. Their internal drive to produce a given quality is the reference voltage. What output the currently have (the progess towards the objective) is the input. When you put top performers in a group to pull up the slackers, the feedback gain of that system is artificially reduced. The good students want a certain level of quality, so they will work even harder to try an bring the quality (input signal) up to their standards. Depending on how bad the slackers are, the good student may even reach saturation, running out of hours in the day to compensate for the incompetence of others. The incompetent teachers intuitively understand this effect. They are not fostering some kind of social nirvana, they are transferring the workload of pulling up the class average onto the bright kids. The bright kid ends up spending twice, three times as long on the group assignment, and that effort gets averaged out to the other group members' grades. The cost to top performers is all that time they could have been improving, moving forward, was stuck doing large amounts of low skill work.

megaman22 11y ago

All of these things you are describing are a good way to waste large amounts of time without getting anything worthwhile done. The 5% where you are not interacting with others is the tiny sliver of time you are afforded to actually produce the product that the rest of the business is built on. With the correct group of people, all of this feel-good communication can be replaced by a handful of people that know what they are doing, keeping an online task board updated and communicating primarily asynchronously by email, or if absolutely necessary, synchronously by IM. Pair programming is a great way to make two people half as productive as either would have been working alone.