Working alone or in a team ?
-
If the project is small enough for one developer to do then I agree completely with your manager. Evidence can be found everywhere, for example a busy restaurant kitchen is often more efficient and able to put out more dishes the less people you have working in it to a certain point. The reason is that large teams are often brought down to the level of the weakest members. One good developer can out code 10 or more mediocre ones working in a team and the reality is that good developers are in very short supply; you do the math. :) When you are talking about a team you are really talking about a committee and for centuries mankind has been fully aware of the lack of efficiency in a committee to do anything: http://thinkexist.com/quotes/with/keyword/committee/[^]
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
modified on Thursday, July 10, 2008 12:35 PM
John C wrote:
If the project is small enough for one developer to do then I agree completely with your manager.
I don't know how you monitor the size of project. The project which I am working is still on development since 1 year. AFAIK, it's a big one or a medium sized one, Right ? Thanks for replying me.
-
Stuart Dootson wrote:
I feel the success (or otherwise) of solo working depends on how happy you are to direct your own work and how responsibility you're happy to take.
I am happy with the work, but when project becomes big, it's hard to remember whole modules. One advantage I felt with solo model is, we are free to take decisions.
I think the main advantage of team working is that you have more options to choose (yours and your teammates). I've done a couple of solo projects and took some horrid decisions that, had I had a parthner, he'd had strangled me. When in a team, you analize your decisions better, because you want your mates to understand why yours is a good choise. You also learn from the experience of your mates, who have solutions different to your owns. And in the end, you end taking the best choises your team can come up with, instead of only what you can come up with. Also, when actually programming, you can share good practices among your team. This improves the quality and efficiency of everyone's work. It's like being capacited all the time. Also, having the need to make your project understandable to the rest of the team, you document your work more carefully. This means that if (when) you leave the company, someone will be able to mantain your project with less effort (meaning less time and costs for the company, if to convince your boss).
-
John C wrote:
If the project is small enough for one developer to do then I agree completely with your manager.
I don't know how you monitor the size of project. The project which I am working is still on development since 1 year. AFAIK, it's a big one or a medium sized one, Right ? Thanks for replying me.
To me a year is a small project for one developer. My largest project took 3 years of initial planning and development. Personally I like to work on something myself and have complete control over it so the length of time it takes is irrelevant to me because it's not about the amount of work at all, it's about having no one else looking over my shoulder or interrupting me while I'm trying to get on with it. I wouldn't do very well in a team of even one more programmer unless the work was divided into big separate chunks. I like to get things done, not talk about it endlessly. My personal nightmare of coding would be stuck working in a cubicle somewhere on tiny peices of some huge application but to each his own.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
-
The company which I am working believes in solo programming and not in team works. Each programmer will be assigned to a project and he/she has to do it alone. This is something new to me as my last company works with teams and I believe team work has more advantage than going solo. I got irritated and presented my worries to the manager. He said "I have 20 years experience in IT industry and from my experience solo programming worked always better than a team". I am surprised ! I argued to my best to prove he is wrong, but I couldn't prove my point as I am not much experienced like him. I just want to get your opinions on this ? Do you believe solo programming is better than a team work ?
That all depends on your astrological sign. As an Aquarius I am independent and don't trust anyone else to get the job done right. ;P
-
Great. I am in the same situation. I given my resignation and waiting to get relieved.
-
The company which I am working believes in solo programming and not in team works. Each programmer will be assigned to a project and he/she has to do it alone. This is something new to me as my last company works with teams and I believe team work has more advantage than going solo. I got irritated and presented my worries to the manager. He said "I have 20 years experience in IT industry and from my experience solo programming worked always better than a team". I am surprised ! I argued to my best to prove he is wrong, but I couldn't prove my point as I am not much experienced like him. I just want to get your opinions on this ? Do you believe solo programming is better than a team work ?
And what happens when the solo programmer for a project gets ill, or dies? I think that would put huge strain on the project as the new programmer would have to learn everything from scratch.
"I'm about as expert as a palsy victim performing brain surgery with a pipe wrench." Check out my site at JacquesSnyman.co.za ** Remember: An article is only as good as the votes it gets **
-
And what happens when the solo programmer for a project gets ill, or dies? I think that would put huge strain on the project as the new programmer would have to learn everything from scratch.
"I'm about as expert as a palsy victim performing brain surgery with a pipe wrench." Check out my site at JacquesSnyman.co.za ** Remember: An article is only as good as the votes it gets **
I think the guys boss' 20 years experience proves that's not as much of a problem as you're making it out to be. It happens but that's an act of God so it just goes to show that there are things more important in life than work and business.
-
The company which I am working believes in solo programming and not in team works. Each programmer will be assigned to a project and he/she has to do it alone. This is something new to me as my last company works with teams and I believe team work has more advantage than going solo. I got irritated and presented my worries to the manager. He said "I have 20 years experience in IT industry and from my experience solo programming worked always better than a team". I am surprised ! I argued to my best to prove he is wrong, but I couldn't prove my point as I am not much experienced like him. I just want to get your opinions on this ? Do you believe solo programming is better than a team work ?
In large-scale projects, working SOLO isn't an option. (a 15 man programming team, part of a 60 person group working on a 2 year crash project, is one of the projects i participated in, as the SW group manager, and system engineer). In smaller projects - you got the answers. You just have to figure out what's best for you. I myself, am a team player. In a team, your strong points become an asset, and if the correct team was assembled - your weak side doesn't show. It's all a matter of balance between technical skills, personal qualities, and management. I was lucky to spend most of my 20 years working with friends. And if you know to draw the line (or border) between friendship and work, and maintain both - it's the best possible work environment.
noams66
-
The company which I am working believes in solo programming and not in team works. Each programmer will be assigned to a project and he/she has to do it alone. This is something new to me as my last company works with teams and I believe team work has more advantage than going solo. I got irritated and presented my worries to the manager. He said "I have 20 years experience in IT industry and from my experience solo programming worked always better than a team". I am surprised ! I argued to my best to prove he is wrong, but I couldn't prove my point as I am not much experienced like him. I just want to get your opinions on this ? Do you believe solo programming is better than a team work ?
Solo programming is better than a team in small projects, and save time too. But when you have to run for big project, the solo takes too long time. Because in small project you save the communication time between the team member And I big project you save the solo programmer time ( and I this case it is too long time).
-
The company which I am working believes in solo programming and not in team works. Each programmer will be assigned to a project and he/she has to do it alone. This is something new to me as my last company works with teams and I believe team work has more advantage than going solo. I got irritated and presented my worries to the manager. He said "I have 20 years experience in IT industry and from my experience solo programming worked always better than a team". I am surprised ! I argued to my best to prove he is wrong, but I couldn't prove my point as I am not much experienced like him. I just want to get your opinions on this ? Do you believe solo programming is better than a team work ?
I work in a co which is geographically dispersed and where we are supposed to be "Mean and Lean" - meaning to be multi-skilled. With three developers on the one side and two on the other, we regularly meet to discuss issues and tips and tricks. We all work alone on your own projects, but with a difference. We each are "King" in a specific area and we share the knowledge between us, or give a call if you get stuck. I am more the one who collects sample code, articles (mostly from Code Project) and the others do other stuff and we share, such as we have a master in MSSQL who I call regularly for tips - we use VC for communicating and once in a while a visit. So my thoughts are, if you work alone, you are stuck with ONLY YOUR ideas. If you cannot confer on a regular basis with the rest of the team, use sites such as this one to broaden your experience and skills, focus on specifics to become a master in that field and build your own components - AND ADVERTISE it to the rest of the team (ans manager) what you do. I think your manager may have a point if there is no clear-cut team development guidelines and may have had some experience in it. On the other hand, I think if each one pulls on it's strengths, you may make a great team, yeah each one managing his or her own project, but have at least fortnightly meeting to discuss each others projects and progress. I think, once the manager realises there is more potential to work as a team, he may re-consider. Below is a slogan I am using for years now - I live it -and it works. T.E.A.M. Together Everyone Achieves More Hope I have given you some ideas to chew on.... Cheers
the confused are confused beyond confusion
-
Working SOLO not beneficial for both company and developer. With the Company Perspective : 1) Only one guy is aware about project. It that involved guy left the company project may be in risk. 2) Company cannot meet the deadline at time. 3) There is different pahse of SDLC. Which cannot be followed by only one guy. 4) Company expectation will be higher than output. 5) Project will loss the standard. It will not be 100% bug free, User friendly and performance centric. 6) Project maintainance cost would be increased. With the Developer Perspective : 1) Working alone become boring job. Nobody will be discuss about project. And you cannot share your problem with anyone.(Like me) 2) You cannot fullfill company expectation on time. It will down your image in company. 3) You will be depend on internet for finding your solution. 4) You will be moody about project. Because project is only in your hand. And you have to decide its "to do list". So you will prepare this list according to your convenience. 5) You will choose very easy way to find the solution. Because you dont want to take risk. 6) Updating yourself will be tough because no comptetion with you. Its all happened with me. I left that company and now i am in team as Team leader in my new company. :)
man i read ur Message Today i think that i should also resign from my company and deepak appkai ic message sai shahid pakistan or india mai boht sai software house apkay dushman ban jain kai app unkai developer ko kherab ker rehai hain ;-).
wasim khan
-
Working SOLO not beneficial for both company and developer. With the Company Perspective : 1) Only one guy is aware about project. It that involved guy left the company project may be in risk. 2) Company cannot meet the deadline at time. 3) There is different pahse of SDLC. Which cannot be followed by only one guy. 4) Company expectation will be higher than output. 5) Project will loss the standard. It will not be 100% bug free, User friendly and performance centric. 6) Project maintainance cost would be increased. With the Developer Perspective : 1) Working alone become boring job. Nobody will be discuss about project. And you cannot share your problem with anyone.(Like me) 2) You cannot fullfill company expectation on time. It will down your image in company. 3) You will be depend on internet for finding your solution. 4) You will be moody about project. Because project is only in your hand. And you have to decide its "to do list". So you will prepare this list according to your convenience. 5) You will choose very easy way to find the solution. Because you dont want to take risk. 6) Updating yourself will be tough because no comptetion with you. Its all happened with me. I left that company and now i am in team as Team leader in my new company. :)