Programming Team Size, and do they all do?

[Guy Davidson]

Gdeaver, we hope to eliminate this problem by having twice / three times a week meetings between the build and programming leaders.
We will probably all be working on all code together, so that should hopefully make it easier to share, assuming it's well-commented. Which is a pretty big assumption

[shawger]

I think with this many programmers you have some great options not available to many teams, but you will have to figure out how to be organized.

You should definately use a source code control system like subversion or CVS. That way, multiple people can work on different areas of the code at the same time, and then merge their changes together. With proper commenting on each commit, this could also help as a documentation tool.

You can also create branches in a source code control system. Maybe there are two or three different ways you could solve a problem. Why not create a new branch for each way, try them all out, and see which one works best?

Also make sure you keep documentation on the code as you write it. Last year, I wrote the code and wrote the documentation afterward. Given that I was really the only one doing the programming, it wasn't a big deal for me. However, it took awhile to do, and with many people working on the code, everybody will need to know how it all works.