|
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
