[dm0ney]

I think scheduling a meeting say Wednesday night while those other three members are uncrating the robot @ Nat'ls might be the BEST time for us to meet.
Feedback? It seems Tom is our main mentor right now, so Tom?

I know that once Thursday comes, programmers will be working quite hard all day and then by Friday and Saturday, it'll be TOUGH to get us out of the stands / pits / watching the matches.

Back to the arm modules...
this year we had a tcr_joint struct with accessors, mutators that we applied to two of our joints ((linear) shuttle / (rotate) four_bar). I think that as programmers, we should all look through our code and see what modules we can pull with minimal ease.

As I see it, the most important thing to this is going to be documentation either with the most complex code or pseudocode so that many programmers can hit the ground running.

I know that our code makes heavy use of pointers, structs, and the like.
Back to the graduated codes... might we also have a ranking system in place on this repository of difficulty of coding / understanding / experience?

We will also want to try and have modules be modules with same implementations because I know supposing a joint module is used like ours and then another joystick module is used from another team, there could be problems in controls.

Another thing we should try and work into are implementing macros into these modules so as a way of graduation maybe, you can enable or disable macros in code.