I'm programmer, operator, and I designed the scouting system/often have to go fix it when somebody does something weird. It is good - I know exactly what to change in the code when I get back to the pit, so it takes half as long as it took last year to fix the problem, because it doesn't have to be explained to the programmers. That leaves me with enough time to check with the scouters and get information for the upcoming matches, and then go work on strategy. Tight schedule, but it works.
Quote:
|
Our lead programmer was the driver last year and this year; he is the best driver on the team. Last year, sometimes he would stop driving to think "gee, what in the code cause that behavior", but we cured him of that right quick.
|
I understand that. I started operating last year, but at that point I was all mechanical/scouting and no programming. This year I am the only programmer, and when we were practicing at home, I would catch myself doing that. By the end of Thursday, though, I was cured of that problem (except during auto).
Quote:
Just don't let them make the control board.
My .02
-Keaton
|
I disagree
. I made the control board last year, and that is part of the reason I operated. I knew the controls inside and out, and no one else really did. This year, I built them again, and it is nice. I have the exact controls I want, and I have them programmed the exact way I want.