|
Solo always first 
|
|
|
|
|
I like the team work. But i Don't like ego and attitude in team
|
|
|
|
|
The difference is big.
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.
|
|
|
|
|
 +1
M.D.V. 
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.
|
|
|
|
|
The idea / architecture phase is definitely a team event but once you have that right and the communications channels remain good the actual coding of components can be team or solo.
|
|
|
|
|
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.
|
|
|
|
|
Indeed - one of the biggest problems with team development used to be base-class contention and now it is model contention. Anything you can do to reduce this will make for a better outcome.
|
|
|
|
|
Hans down Solo, but sometimes you're Forced to Wookie in a team.
|
|
|
|
|
Artoo? 
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.
|
|
|
|
|
That is a wall everyone (Browsing CodeProject to learn more) keeps on hitting. But I don't think that any of them can do something about it (or at least climb it).
|
|
|
|
|
Sure you can do something. When they came to assimilate me into their team, I told them that I already had forgotten more about programming than they and their team ever had known. After that, working on this particular project became bearable. At least most of the time. The price for that was to look for another place to work, of course. If I wanted to join a religious sect, I would have done that without their help.
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript.
|
|
|
|
|
Coding is akin to an artist working on a painting. A single artist can produce a cohesive and beautiful work of art. Multiple artists will have different techniques and while the final product may or may not be interesting, it's rarely a masterpiece. However, if the project is a giant mural or covers a city block, it's not practical for a single artist to complete. Likewise, there are projects where sheer size dictates the need for multiple coders. So I'm voting preferably solo, but a team for large projects.
|
|
|
|
|
I was a fine artist before becoming a coder (many many years ago). The transition was easy since the approach, process and creative practice were the same. This is a truth the industry refuses to recognize.
|
|
|
|
|
Strongly agree with "Coding is like art..."
When working in a team... too many ideas for solving a single problem...
Too many cooks spoil the soup
http://www.zapiro.com/Cartoons/m_101125mg.jpg[^]
But the problem of solo is.... it will take plenty of times to complete a large project alone.
So... em... I'm in the process of learning to work in a team...
|
|
|
|
|
Because I get to play god and make all the decisions and direction. Beside I don't have to please anyone other than myself. Team works when the team members have like mind set, especially ego.
|
|
|
|
|
If you are a part of a team do not seek the guy how learns tow steps ahead of the team. LEARN IT YOURSELF.
|
|
|
|
|
I have been an independent contractor/consultant for many years so I obviously support the solo coder; still, I have learned to find the most talented member of the team and forget my self-image. Just watch and learn. If I discover that I am the most talented on the team, I take the opportunity to mentor others into becoming confident, talented SOLO coders who eventually start their own businesses.
Not like Managers who like to keep the herd in place with policies, procedures, group-think and control; if you are in this situation, get out. Never worth it.
The worst type of team is "The Brotherhood"; the coding fraternity, who demand your complete allegiance. Should just kick them out into sales where they belong.
|
|
|
|
|
If it support I can provide. However, When I'm on the run for the last day before a deadline, I can't help but wish I was a less of a nice-guy and kick them out.
|
|
|
|
|
While code teams are often necessary; I have worked well in quite a few, the process of coding is similar to fine art in which the artist faces a blank canvas on which an idea must be designed and created. As in art, code is the realm of the individual mind.
Minds of mediocrity demand an assembly line process in which coders are interchangeable. They establish cliques of hive minds in which everything is collective. They make religions out of processes and procedures and demand the same zealotry of others.
In my decades in the profession I have found these team-only disciples to be people of little talent with no innovation or creativity. They conceal these inadequacies by hiding within groups: teams, pair-programming, hive-mind reviews.
Individuals create; groups consume. Every major innovation in history has been that of the individual. Of course, teams developed the atomic bomb and we know that result...
|
|
|
|
|
And you will never get to really experience the sorrow unless you are forced to make a mediocre mind into a creative one (WITHOUT USING MAGIC).
But...
Imagine tow or three Creative minds working together. What they can do, What they can Make!!!
|
|
|
|
|
Mediocrity hiding within the collective "we" of a team should be exposed and driven out of the industry; unfortunately, this "team sports" approach to coding creates a sanctuary for them and drives talent away.
When I lead a team, I follow neither code dogma nor implement stringent procedures. I allow each coder to develop as he or she feels most comfortable. If the coder is a complete introvert who prefers to develop at 3am while wearing two hats; so be it. I had and have only three rules: keep your promises, be ethical and make sure I am impressed by your work.
|
|
|
|
|
What if you can spot mediocre minds and stay away from those circles.
Working with people of the same height and coding sight, Making sure to finish all the important projects leaving the rest to... do whatever they do.
|
|
|
|
|
I like going solo if it's a small project (Yes, I fix all the bugs myself). But I also like having a team for bigger projects. When I'm stuck, there are others to bounce off ideas. Also, it's fun in the break room and going to lunch together.
|
|
|
|
|
...as long as they do everything my way! 
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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
