Quote:
Originally Posted by DiscoKittyPrime
This topic was brought up by one of my mentors after the end of championships this year. I was the head programmer on our team for the past two seasons and am leaving the team for college next year. We have a programmer who will take over next year but he will be a senior then and we don't know who else can be brought in after he graduates. This is a concern for us and I asked how the team recruited programmers in the past.
snip
|
Of the 30-odd members on our team next year, it seems there will be at least 5 programmers. I'm pretty sure we only need 2. I'm game for a trade; no one here knows how to do a decent CAD, and I'm left teaching myself...
In all seriousness, try to get people to "double major" in the subsystems of the team. Whoever is doing wiring would be a great candidate to read a few LabView tutorials and become a programmer. Not to mention, this person doesn't have to constantly communicate the ever changing pin layouts in the Digital Sidecar or remember how many Victors he/she has to code for. This avoids night-before-ship dialog like this:
"I'm sorry Jack, I can't remember the slot for this PWM."
"Just wing it, I'll deploy and we'll wing it."
"What."