[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ProgSoc] bent over and ...
> You did part of the assignment and our partner did part, presumably
> demonstrating that neither of you had a complete grasp of the
> Your lecturer found out about this and failed you.
One little question though, if a group is not going to split the workload
then why bother having a group, you might as well do it yourself. In fact
a group that does not split workload is actually less efficient than an
individual because they spend all their time arranging meetings, arguing
over decisions and grinding along in committee mentality.
Some things (like legislation) are well suited to being ground out
slowly in this manner. Software is better when done by only a few people
(at best only one). Thus, the sensible way to do a big software project
is to make clear divisions and give one section to each person with only
the interfaces left to committee. One such division that is commonly used
in industry is separating coding from documentation and yes usually the
technically brighter people (usually male) do the coding and the more
literate do the documenation (usually female).
The male/female ratios are drifting but haven't drifted much.
Naturally the end result of this is that each becomes a specialist in
their own area. Take a look at our society -- full of specialists.
> > Also, if anyone has some advice, i'm sure this has happened to atleast one
> > of you renegade progsoccers over the years, 'twould be greatly
> > appreciated.
> My advice - if you're going to do things like this, don't be silly enough
> to get caught.
In other words, don't openly expose the gaping gap between a lecturer's
theoretical concept of correct and how the world really works. I've got to
agree with you there, asking people to face reality is a guaranteed way of
pissing them off.
You are subscribed to the progsoc mailing list. To unsubscribe, send a
message containing "unsubscribe" to firstname.lastname@example.org.
If you are having trouble, ask email@example.com for help.