What do your programmer's do (besides the robot)

[hardcopi]

Ours come up with more and more disturbing plans to take over the world. We try to keep them busy.

Another good thing is documentation. We lost most of our programmers this year, but thanks to documentation (and the fact that they are teaching weekly classes to newbies until they leave for College) we are going to be ok.

FInd some reusable bits of code for them to improve upon. A favorite of our team is the joystick conditioning code.

[FlamingSpork]

Originally Posted by hardcopi

Ours come up with more and more disturbing plans to take over the world.

Always fun to plot, but when you actually try, you get a segmentation fault.

I'm working on coding a field management system for Maize Craze, and I so far have learned that any line of code can cause a segfault.

My team has also been working on learning how to make our code a tangled mess based on this: https://www.thc.org/root/phun/unmaintain.html

[GeeTwo]

This year we're requiring all of our programmers (and all of our controls people, and all of our mechanical people) to take a job on the business side of the house as well. "Business" includes just about everything that doesn't relate to the robot build, including Chairman's submission, outreach, web/social media, fund raising, scouting/match strategy (though not build strategy), spirit, safety, and probably a few more things I can't think of right now. The concept is to have separate meetings for "business" vs "technical". During the "off season", there should be a business vs technical breakdown approaching 1:1. During build season, this will probably be more like 5:1, or perhaps even worse.