[Boydean]

All these things are really good. Ill just add in my two-cents.

A. Get someone on the team that is pretty good at logic. It doesn't need to be someone that really is into programming. Get them to sit next to you and walk through the program with them; step by step. This will kill alot of debugging time when the robot it ready for real testing. Trust me it works.

B. Write comments in your code...and some more comments. It doesn't matter if your the only programmer writing comments just for your self will help a lot. Its the simplest thing to do but yet the easiest thing to forget.

C. If you have any limits on your robot, stuff that prevents your robot from killing it self. Program thoughs first, before you test anything make sure those limits work. Its one thing to sitting around waiting for the mech. guys to get the robot done, its something else watching them fix it when it just killed it self.

All the advise mention is great. This being the fourth year being the only programmer on our team(1 FLL, 1FVC, 2FRC). Just remember, its tiring to program but not as tiring as sawing and drilling. So its up to you to keep the energy flowing at all times(just a little something random). Good luck!