How to choose programmers?

[TimTheGreat]

One of the things that is helpful is for those who want to be programmers to be in computer science in order to know 'programming'. That is, how if statements work, return, while loops, for loops, that kind of thing. It is easier for a person who is trained in teaching students to teach them how to program than it is for a mentor or another student to try. Even so, our team created a python training module that you can find here. We went through this as a group and now most of our team is somewhat up to speed.

We don't actually pick people, instead they tell the captain they want to program, and that is that.

[yash101]

There are multiple ways to go around with this.
I really suggest to pick people with at least a little bit of programming background, at this moment of time, as we are really close to the new season.

In my programming club, I have it as open enrollment -- anyone can join -- no experience required. Of course, this means that you need to know how to use a computer, and how to install software, for example.

This "open-enrollment" option means that you will tend to spend a lot of time just teaching students the basics of programming.

If you get students that know how to program, even in just a different language, say Python instead of C/C++/Java, they should be able to catch on quite quickly.

[Rangel]

From my experience of my team as well as talking to many others, programmers are pretty rare on most teams. You really can't have enough considering how many potential programming projects and problems there are so I would take anyone that is interested. Whether or not they are dedicated is another story but that's why you have them work with someone more experienced or have them work on smaller projects before you give them a really important task.

[Roger]

How to choose programmers?
It's the ones you have to pull away from the computer and shove out of the building late at night.
(And the obligatory "cans of Mt Dew and bags of chips".)

[Sparkyshires]

On the "if interested, join." aspect, my team had an issue with that last year. We had about 8 people interested in the "romantic" esque aspect of programming, as in they wanted to become like super hackers or something. However, come build season,after teaching them all the way from September 1 to January 1, we had on average maybe three for the first three weeks, and then we were lucky to have one or two of the original 8 every night. I'm also trying to find a way for our team to find new programmers, that are capable and willing to come.

[dash121]

I think the idea of a "patience game" is perfect for at least the text based languages. I think that would be the best way to do it by far! Thanks so much from all of you!