View Single Post
  #6   Spotlight this post!  
Unread 13-10-2014, 14:50
Oblarg Oblarg is offline
Registered User
AKA: Eli Barnett
FRC #0449 (The Blair Robot Project)
Team Role: Mentor
 
Join Date: Mar 2009
Rookie Year: 2008
Location: Philadelphia, PA
Posts: 1,112
Oblarg has a reputation beyond reputeOblarg has a reputation beyond reputeOblarg has a reputation beyond reputeOblarg has a reputation beyond reputeOblarg has a reputation beyond reputeOblarg has a reputation beyond reputeOblarg has a reputation beyond reputeOblarg has a reputation beyond reputeOblarg has a reputation beyond reputeOblarg has a reputation beyond reputeOblarg has a reputation beyond repute
Re: Advice for teaching new students

Make sure that your programmers don't only know programming. I've found that ensuring programmers have a healthy understanding of electronics and mechanics serves several purposes:

1) For those students who don't continue with programming (there will be many of them, trust me), it provides a much easier transition to productive work elsewhere on the robot

2) For those students who do continue with programming, it makes them far better at their job - you can't program all that well if you don't understand the mechanisms that you're trying to control.

3) In general, I think it is good pedagogy to have every student have some level of understanding of all that goes into making the robot function, even outside of their specialization.
__________________
"Mmmmm, chain grease and aluminum shavings..."
"The breakfast of champions!"

Member, FRC Team 449: 2007-2010
Drive Mechanics Lead, FRC Team 449: 2009-2010
Alumnus/Technical Mentor, FRC Team 449: 2010-Present
Lead Technical Mentor, FRC Team 4464: 2012-2015
Technical Mentor, FRC Team 5830: 2015-2016

Last edited by Oblarg : 13-10-2014 at 15:55.