|
It all depends on who you work with. If I am around a group of developers that have fairly good skills but do not have my level of expertise on the particular subject at hand I perfer to get the project up and going. Once the foundation or simply the direction of the project is layed out it is fine to work with multiple people. There is nothing more annoying then trying to justify every decision you make to someone who hasn't a clue about the subject but has to try and sound like they do so they feel better about themselves.
|
|
|
|
|
Yes,that's right!I perfer to get work with the boy who have the same minds with me to the project,but not the sel-satisfy gids.I hate that someone always aguring with me about this and that,becase it is hard to get work,isn't it? 
|
|
|
|
|
I have almost always worked alone, no matter what type a job I have had.
Working alone gets to you after a while (years). I prefer working with a least one other person.
INTP
|
|
|
|
|
i agree. - it gets to you after a while.
my mind is going bananas.
luckily my memory is good. i replay southpark episodes in my head all the time.
|
|
|
|
|
If we are working with genuine then 2 to 3 are more than enough, but I happen to see companies hire more number of morons and VERY few of them are genuine, so its difficult to suggest !!!!
|
|
|
|
|
The correct number of developers for any project is an odd number
((n % 2) != 0).
However ... three is too many!
bool bCorrectNumber == ((n % 2) && n < 3);
The opinions expressed in this communication do not necessarily represent those of the author (especially if you find them impolite, discourteous or inflammatory).
|
|
|
|
|
You could've just replied "Alone", you know. 
"if you vote me down, I shall become more powerful than you can possibly imagine" - Michael P. Butler.
Support Bone
|
|
|
|
|
for me it depends on project size and time available to complete.
Sonork ID 100:25668 Home Page
|
|
|
|
|
Yes, but what are you saying?
More developers does not mean more productivity.
Neither does less.
Small projects are not always easy, successful or efficient.
Neither are large ones.
More time does not mean more success either. Often a a tight deadline inspires. We developers get lazy if given too much time (and run about like headless chickens if the timeline is ludicrous.)
So, given your average project size and available time, what do you prefer?
regards,
Paul Watson
Bluegrass
South Africa
Brian Welsch wrote:
"blah blah blah, maybe a potato?" while translating my Afrikaans.
Crikey! ain't life grand?
|
|
|
|
|
More developers does not mean always more productivity.
For a given average project size and available time, I will prefer 2-4 developers only.
Sonork ID 100:25668 Home Page
|
|
|
|
|
Well, I am basically alone in our windows development which has its ups and downs. My current project is around 500K lines and 60 to 75% of that was me alone... The rest is from either codeproject or my coworkers. I find that most of the code I get from codeproject is a good start but I have to modify it to suit my needs. Being the only developer on a project of this size requires me to spend a lot of tima at work and sometimes I think I live at work... And code maintanance is often put off because I am constantly given new features that must be implemented two weeks ago... But I have my own office. Have a lot of control over computer purchases. I get a new PC every 6 months... And I have a lot of job security.
John
|
|
|
|
|
I wonder how many people have a result that is close to their ideal.
|
|
|
|
|
Good question. I bet several people do, though.
It is interesting that (as of the time of this writing) nobody has voted for "as many as possible". I don't think I'd vote for that, either... I have images of 20 programmers all trying to check out the same file to make a change... 
No single raindrop believes that it is responsible for the flood.
|
|
|
|
|
Many programmers means a lot of Managment means shitfloods every day.
"Vierteile den, der sie Hure schimpft mit einem türkischen Säbel."
mlog || Agile Programming | doxygen
|
|
|
|
|
Not quite the way that I would have expressed it but absolutely true
In my experience, though, what tends to happen in practice is that the management do not really manage because things are too complicated and leave the decisions to those who shout loudest. What happens then is like an orchestra without a conductor....
|
|
|
|
|
What about open source initiatives?
Just throwing it in
regards,
Paul Watson
Bluegrass
South Africa
Brian Welsch wrote:
"blah blah blah, maybe a potato?" while translating my Afrikaans.
Crikey! ain't life grand?
|
|
|
|
|
::Consisting of 1000 people "yeah I really once like downloaded the sources for that" and 5..10 working their prolonged back side off?
Admitting that I don't know stats of any OpS project, but those "joint movement" things are usually made a success by a few people knowing what they do and a gazillion of cheerleaders staying out of their way.
"Vierteile den, der sie Hure schimpft mit einem türkischen Säbel."
mlog || Agile Programming | doxygen
|
|
|
|
|
What about something like the Linux core which is undeniably succesful. Anyone can contribute but hand picked chiefs as well as Linus pick what is officially put in? People focus on what they are good at and interested in, e.g. disk IO, and the best code is the one that is used. People can collaborate or not, up to them.
Naturally Linux seems to have been blessed by Linus who has walked a fine line.
regards,
Paul Watson
Bluegrass
South Africa
Brian Welsch wrote:
"blah blah blah, maybe a potato?" while translating my Afrikaans.
Crikey! ain't life grand?
|
|
|
|
|
my question being: How many people have really, subtantially, contributed to Linux?
Linux itself probably isn't that bad (but some thread I read about it some time ago did sound like the same ole' sh*t flying around). But with other OS projects... hey, well. Maybe I just don't like them
"Vierteile den, der sie Hure schimpft mit einem türkischen Säbel."
mlog || Agile Programming | doxygen
|
|
|
|
|
Paul Watson wrote:
What about something like the Linux core which is undeniably succesful
AFAIK the core has been splitted in several semi-independed projects (virtual memory, scheduler, block device access etc), each with a number of active developers that is well within the managable amount.
The final integration of the part is what Linus mainly does.
Who is 'General Failure'? And why is he reading my harddisk?!?
|
|
|
|
|
"What about something like the Linux core which is undeniably succesful"
Could it be success in commercial point of view. Will any Open-Souces Project ever be commercially success.
|
|
|
|
|
...that's a bit of a twisted question. 
Many open source projects have been sold commercially / used in commercial products / used in the development or support of commercial products. However, i think it's misleading to view these as "open source commercial success".
Step back - how do you define "commercial success"? If you intend to make money through commerce - that is, by selling stuff - then, i'd say you could consider yourself successful if you made or exceeded the amount of money you expected before starting. Given that definition, i'd guess that something like the Linksys routers which use Linux internally might be considered a commercial success.
But - this doesn't exactly have any relevance, as the OS was developed long before someone decided to use it in a router. I have a feeling what Paul meant by "success" was more in terms of "has the project produced software able to meet the expectations of those using it" - which is something else entirely.
A servant to formulaic ways.
Shog9
|
|
|
|
|
This is my first guestimate formula :
(Number Programmers To Consider) = (Number Programmers On-Site) + R x (Number Programmers Working Remotely)
where R is a ratio which will probably at least 2.0. This ratio depends on the quality of the communications, time spent communicating etc, and the quality of the project management, etc.
So for example, if you have a team of four programmers on-site plus two remote programmers who rarely are on-site, the actual number of programmers to consider = 4 + R x 2 = 8 programmers to consider.
Thus even though we only have 6 programmers, we need to plan the project management as though there are 8 programmers, and all the consequential difficulties that arise from having larger teams.
Now if we apply Open Source to this equation, where we have programmers all over the place, the managament issues become massive. But then again, OS is really a different situation because the progrrammers can pick and choose and only do the bits that they are good enough to be able to make a good contribution which is a luxury that we don't usually have in smaller teams.
I think that I should quit now whilst I am ahead
|
|
|
|
|
it also depends on how are the people that you are guiding...
most of the time many people that i've been working with are very good profesionals, but sometimes you find someone that seems to be there to make your life as hard as they can  .
|
|
|
|
|
Yea, the quality of the professionals I get to work with is more important for me than the quantity.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
