View Single Post
  #6   Spotlight this post!  
Unread 06-09-2011, 01:25
AustinSchuh AustinSchuh is offline
Registered User
FRC #0971 (Spartan Robotics) #254 (The Cheesy Poofs)
Team Role: Engineer
 
Join Date: Feb 2005
Rookie Year: 1999
Location: Los Altos, CA
Posts: 802
AustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond reputeAustinSchuh has a reputation beyond repute
Re: A new Programmer

One of the best things you can do to learn how to program the robot is to try programming last year's robot again from scratch. Heck, try to make it even better than last year's code. You have months until the season starts. Try to write a 2 tube autonomous mode. Have fun with the robot. You don't need to know lots of crazy C++ language features to be able to program the robot well. If you find something that you don't understand in WPILib, then take the opportunity to learn about that language feature.

My experience with FRC programming has been that figuring out which algorithm works best to solve the problem in front of me is the hardest part. It is quite hard to figure out how to get the robot to do what you want it to do, and that problem is just as hard to solve when writing pseudo code as when writing C++.

I have also been work for years on how to structure the code in such a way to make it easy to maintain, quick to try new stuff out with, and flexible. It is easy(ier) to write code to get the job done, but hard to make it so that you can fix it quickly when you catch a bug in the heat of competition, or so that it is easy for someone new on the team to quickly get up to speed.
Reply With Quote