Re: Programming Team Size
 

Without an easy way to tell what changes have been made, you're better off with only one person programming the main controller.

As far as diffs, I would recomend KDiff3: http://kdiff3.sourceforge.net/
There are versions for Linux, Windows and MacOS X

Re: Programming Team Size
 

I am currently a one man programming team, with one rookie who needs to learn the ropes of the current code, and then needs to use that for next year, to program the robot.

I for the purpose of showing what changes have been made over a certain week (so that I as the programming team can show that I am contributing to the entire project), I have versioned the entire code into subversion, which allows people to check the code at the same time, and then merge changes into the project.

Makes tracking progress a lot easier, and knowing when things are happening and why. Also the possibility to go back several revisions, to working code, means that there should never be a problem with having code that is not working properly.

Re: Programming Team Size
 

if you guys want a good programming team you need more than one. I'm the lead programmer and not only do I have to teach kids for next year but I have to actually get the stuff done.

There is plenty that my programmers do. Build the camera, program Auton modules, set up the controls, take notes, do research, calculate physics, run tests. plenty of tasks for everyone. if you go a little more in depth.

but I would say no more than 5 probably. plus trainees

Re: Programming Team Size
 

Our programming team size is pretty good. We have Myself, and SubQuantum, who are basically the programming Gods of the team. Then we have a member who knows C, but isn't entirely to our level, and I think 3 rookies. This allows SubQuantum and I to work on the more advanced stuff, such as our proposed Neural Network Autonomous code and the automated Ball turret, while the other 4 do driving code, LED control, and maybe a few simple Dead-reckoning State machines for Auton. mode.

I say Two for the super-advanced stuff, and then a slightly larget team of 3-4 for the mid-range stuff. Either way, for a project like this, I wouldn't go with any more than 6.