|
Ewe are so bad! 
Along with Antimatter and Dark Matter they've discovered the existence of Doesn't Matter which appears to have no effect on the universe whatsoever!
Rich Tennant 5th Wave
|
|
|
|
|
Do you mean a team of one?!
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
We have a single one. 
|
|
|
|
|
By working with a team it is easier to discuss about architecture or ways to solve things.
Besides this I don't like it that only one single person knows about the code of a product. I prefer that all the members of my team can work on any product.
Dreeke
|
|
|
|
|
... for one person to finish solo in a reasonable time frame; some are too small to work sensibly with two or more people.
It's a balancing act: if there is more than one man-year of work, it is definitely team material. If it's less than a man-month then it's probably solo.
Having said that, I haven't worked in a team for twenty years... 
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
The way I see it:
Some projects are just too big for a team of people to finish in a reasonable time frame; some are too small to finish solo - it will get done way too quickly.
|
|
|
|
|
OriginalGriff wrote:
Having said that, I haven't worked in a team for twenty years...
LoL
|
|
|
|
|
If I can do it myself and am familiar with the code, then I work on my own.
If I am not familiar with the code, then I prefer a team. Always nice to see some expertise when coding around me.
|
|
|
|
|
seem to be reasonably sensible, no one has voted for number 3. Some pillock will naturally vote for solo - large, team - small before the week is out.
While I prefer solo work it just does not make sense on large projects, not with a reasonably delivery time at least.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Don't you yearn to work on a large project solo? You get to architect the entire thing, make decisions that span a massive system knowing that the entire thing will be consistent and along the lines of your thinking, not bent by someone else's?
(and of course with your own consistent architectural errors and bugs  )
cheers
Chris Maunder
|
|
|
|
|
Gods forbid, working on a project with multi year delivery profile is one of the truly horrifying things that could happen to me. While I have worked on such a project when I started into it the horizon was a couple of months, the most amazing case of scope creep I have ever heard of.
I find my willingness to accept that I screwed up has saved me from compounding errors that I have seem turn into the most terrible, unsupportable kludges around (SAS comes to mind along with blotus)
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: find my willingness to accept that I screwed up
The most valuable skill a person can have, bar none.
cheers
Chris Maunder
|
|
|
|
|
It simplifies the search for guilty...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
Also good for version control.
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Lots of the radio button items asks what I prefer. The survey subject asks what is better.
My preference is not necessarily better. There is a brotherly- and social aspect of working in a team. That is not to say that it is always better than working solo. Don't get the two mixed up. This should have been two surveys... 1) Which is better. 2) What do you prefer.
The important part of bug finding&fixing bugs is not necessarily the fixing of it interdependently, but rather the finding which should be done interdependently- or even better... by more than one party (coder and tester). It is more difficult to find fault in ones own code than if someone else checked it. Point being: Why compare apples and pears... coding in a team does not mean coding and testing but you use it as if it were interchangeable. I can code by myself but still be part of a team that is working on a project with a couple of people testing my code, and fix the bugs they find myself.
"Program testing can be used to show the presence of bugs, but never to show their absence."
<< please vote!! >>
modified 17-Mar-14 3:30am.
|
|
|
|
|
As a hobbyist programmer I have never worked on a team. So it is solo only.
Within you lies the power for good - Use it!
|
|
|
|
|
|
So...why don't the two of you get together and work as a team, to see how it goes?
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Splitting work is fine but fixing others bugs are terrible things.
thatrajaCode converters | Education Needed
No thanks, I am all stocked up. - Luc Pattyn
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is - Henry Minute
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
