When you work with others, each one have its own responsibility, blame, and merit.
Everybody is motivated, because their individual work become part of their identity. And nobody wants to damage their own identity and reputation.
When you work in team, every developer share the responsibility.
In this case, no developer feel that the project is part of their identity, because everybody touch it. So they care less when someone, or themselves create crap.
After all, the blame and merits belongs to the team. Not to me.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
However not all components can be developed effectively by a team. If a large component haven't been split up correctly then teamwork is a curse and besides this below a certain component size work can not be performed in parallel that is the most effective way of using time. Ideally all larger components should be split into such small units of work so programming itself is rather individual work. Planning and drinking together is teamwork. Solving together a small unit of work? How many mothers are needed to give birth to a child earlier than 9 months? Leaders who think that putting more people on things is an effective way of cutting down from the production time are wrong.
Anything that is unrelated to elephants is irrelephant Anonymous ----- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 ----- I'd just like a chance to prove that money can't make me happy. Me, all the time
Teams are fine; when appropriate. The current and popular team attitude is not.
Having been a coder in the profession for almost two decades; as an independent consultant the latter half, the most troubling aspect I have seen is to be found in the current manifestation (more like infestation) of coding as a team-only activity dedicated to the assembly line.
Most coders were; and probably are one of the following: nerd, goth, outcast, loner, artsy, dork, gamer etc. Of them in the past, our industry exists because of these outcasts and loners.
Now younger coders form teams in which each member must think the same, act the same, sit side-by-side, never stand out and never, ever be a "lone wolf". What happened! Now to be a successful coder, you cannot be a loner or outcast?
The coding profession was created and populated by non-conformists; give me a talented weirdo over one of the "dudes" any day. A coder who can talk for hours about futurist concepts, I trust. One obsessed with sports and "the team", not so much.
That is the problem with many teams: they have become social fraternities.
Last Visit: 31-Dec-99 19:00 Last Update: 28-Dec-14 20:59