|
Re: Should a programmer be a driver too?
Great feedback, thanks! My one concern is that our drivers are usually busy with strategy meetings, driver meetings, and of course being in queue and on the field. Normally our programmer works on the code during those events changing what the drivers have requested. How do you do both jobs simultaneously? I'm open to the possibility (that's why I asked), just want to know about how to handle the dual-responsibility. The programmer is really the only team member who knows the code well enough to make changes... just makes me nervous to stretch anyone too thin?
Thanks!
__________________
2014 Buckeye Champions - thanks 846 & 639, Troy Champions - thanks 33 & 5193, Imagery, Entrepreneurship & Industrial Design Awards
2013 Kettering Champions - thanks 70 & 862, Three Imagery Awards
2012 Western Mich Finalist - thanks 1918 & 85
2011 Trav. City Web Site, Troy Xerox, Mich State Semi Finalist & Judges Awards
2010 Kettering Champion - thanks 67 & 70, Kettering Rockwell Innovation 2010 Troy Finalists - thanks 33 & 288, and Rockwell Innovation
2009 Kettering QF, Detroit Finalists Detroit Creativity Award, Troy Semi-Finalists Troy Creativity Award
2008 WMRI Finalists - thanks 1243 and 904, 2008 Kettering Champion - thanks 67, 1075 and 2619
2008 IRI Judges Award Winner, Great Lakes Finalists - thanks 66 & 217, Western Mich
2007 Curie Division Champions - thanks 330 & 1270
|
At IRI you have 72 of the best teams in the country. It could literally be held in a cornfield in the middle of Indiana and nobody would care, because the competition is simply that good. - Cory [more] 
03-03-2009, 00:15
Similar Threads
Threaded Mode