begin quoting Andrew Lentvorski as of Sun, Mar 04, 2007 at 04:15:48PM -0800: > James G. Sack (jim) wrote: > > >- Designing an incremental-iterative one-semester, undergraduate course > >in software engineering > > http://alistair.cockburn.us/index.php/Designing_an_incremental-\ > > iterative_one-semester%2C_undergraduate_course_in_software_\ > > engineering > >(yuk, what an URL!) > > The one things that I absolutely *hate* about all these practitioners is > their emphasis on "group work", "collaboration", etc. for college work. > > Quite plainly: bullshit.
I learned two good lessons about working in groups in College. Lesson #1 - if you have good people, there's a synergistic effect plus it's a lot of fun. Lesson #2 - if you don't have good people on your team, it's going to suck, and picking up another's slack is more work than going at it alone, and you're going to hate it. > You can't work in a group until you can work *alone*. Every human > endeavor understands this except, it seems, software managers. You need > the fundamentals first. Whether it's basketball, cooking, music, > engineering, or software development, the individual skills need to be > automatic before you can handle the added complexity of group dynamics. If they're not, it's gonna to really cause heartburn. BTDT. > If teamwork is that important, then the corps need to petition the > IEEE/ACM to add some group psychology classes to the guidelines. Until > then, the corporations can take their "We want cooperative little > drones, and we want *you* to do all the work rather instead of us" > attitude and go pound sand. Heh. -- "Sequential Collaboration" is both useful and educational. Stewart Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
