Code Structure, Organization, Division of Labor!

[dm0ney]

How do fellow FIRST teams divide up the code for different people to work on it, do version control, and also code structure itself?


At Team #217...
The first week, we mapped out an entire whiteboard with function calls and the like. A pretty basic API which was ultimately the most important thing our team did that first week ;)
We approached the code with two flow charts:
Robot -> Drive, Arm, Vision
OI - > Joysticks, Buttons
We filled in all our required variables, mutators, and accessors. Agreed on naming conventions and then divided the work up like this:

Programmer A = low-level commands / drive / joysticks
Programmer B = pneumatics / study on making TC Dashboard
Programmer C = arm
Programmer D = autonomous / scripting
Programmer E = vision
Programmer F = catch all, implementing all

Ultimately, We went to 3 main programmers... one lost to drive team, one lost to mechanical.

To control versions, we set up a wireless network @ our place of work and had a CVS server that we all learned how to use / taught people how to use.

Our code structure is set up in multiple files, each pertaining to what it is
(encoder.c, pid.c, oibuttons.c, userbyte.c, arm.c, vision.c, scripting.c, commands.c....... etc)
We also approached a style as close to OOP as we could using structs, pointer fun, and init statements and the like.

Parts of our code will be released in the coming weeks and feel free to find our team at Atlanta to see the code display that I'll be putting together.... eventually :)

[AIBob]

How do fellow FIRST teams divide up the code for different people to work on it, do version control, and also code structure itself?


At Team #217...
The first week, we mapped out an entire whiteboard with function calls and the like. A pretty basic API which was ultimately the most important thing our team did that first week ;)
We approached the code with two flow charts:
Robot -> Drive, Arm, Vision
OI - > Joysticks, Buttons
We filled in all our required variables, mutators, and accessors. Agreed on naming conventions and then divided the work up like this:

Programmer A = low-level commands / drive / joysticks
Programmer B = pneumatics / study on making TC Dashboard
Programmer C = arm
Programmer D = autonomous / scripting
Programmer E = vision
Programmer F = catch all, implementing all

Ultimately, We went to 3 main programmers... one lost to drive team, one lost to mechanical.

To control versions, we set up a wireless network @ our place of work and had a CVS server that we all learned how to use / taught people how to use.

Our code structure is set up in multiple files, each pertaining to what it is
(encoder.c, pid.c, oibuttons.c, userbyte.c, arm.c, vision.c, scripting.c, commands.c....... etc)
We also approached a style as close to OOP as we could using structs, pointer fun, and init statements and the like.

Parts of our code will be released in the coming weeks and feel free to find our team at Atlanta to see the code display that I'll be putting together.... eventually :)
My team doesn't have many people who want to program, I am the only student programmer on the team.

But, We also have our great mentor, Mr McLoed... who helps with the code for whatever I cannot do.
.. between us, we really just do everything, every once and a while I see he's added more random code to do some crazy thing and I add some code too and then we tweak the code until it fits and looks good enough.
...but we do not acually divide the code amongst...
two years ago, when I was not the only programmer, it was a little more split, I did more of the autonomous, and they did more of the basic keeping the pneumatics going and making sure the main driving ability was there...

[devicenull]

I'm the only programmer here. I like it like that though, I know every piece of code inside and out, and I don't have to worry about those nasty problems when two people edit the same file :)

I hade a SVN server set up for me.. but I kind of got rid of the computer it was hosted on without even thinking about it.

[ConKbot of Doom]

I'm the only programmer on our team, so that keeps orginization simple for us too. I wish I could have had someone else to split up some of the work though, just as long as they wouldn't hinder me.