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