[Arhowk]

My team's on the complete opposite end of the spectrum- I'm the only programmer (and the head electrical for that matter) with no programming mentor, but I'm just so bad at teaching kids that they get confused and decide to go to mechanical

Firstly, I think that you should start ALL students in robot programming for a few main reasons:

• It's the easiest programming in most of FRC. Teaching kids robot programming can help filter those who have interest in programming against those who just want to be around a computer, but also doesn't shy off the kids who really want to be programmers but don't want to get thrown into hardcore javascript day 1.
• It's the only thing needed by every team. Scouting is nice, website is nice, but you're going nowhere without a robot. If you teach kids web development and robot seperately and the robot programmers turn out to be mechanically focused than you have to teach the other programmers robot programming.
• It's hard to get this kind of experience outside of FRC. Anyone with a computer can build a website but the best kids can do for programming is just buying some $20 arduino kit. Managing code for a $5000 robot on a team of 20+ people is a tough experience to get elsewhere outside of an actual job.

Once you've filtered and sharpened a nice group of programmers (yes, every kid will try to enter as a programmer, its not as fun as they think) you can divide it elsewhere as other posters have said.

As to not be too off topic, "too many" shouldn't even be in your vocabulary! Just be sure to utilize them properly, don't just throw them in a room and tell them to code.