Thread: Lessons Learned
View Single Post
  #2   Spotlight this post!  
Unread 26-05-2011, 02:48
ratdude747's Avatar
ratdude747 ratdude747 is offline
Official Scorekeeper
AKA: Larry Bolan
no team
 
Join Date: Feb 2009
Rookie Year: 2008
Location: Madison, IN
Posts: 1,064
ratdude747 has a reputation beyond reputeratdude747 has a reputation beyond reputeratdude747 has a reputation beyond reputeratdude747 has a reputation beyond reputeratdude747 has a reputation beyond reputeratdude747 has a reputation beyond reputeratdude747 has a reputation beyond reputeratdude747 has a reputation beyond reputeratdude747 has a reputation beyond reputeratdude747 has a reputation beyond reputeratdude747 has a reputation beyond repute
Re: Lessons Learned

my lessons learned for labview code:

1. Always keep teleop.vi nice and light. leave the heavy stuff in periodic tasks.
2. If time allows, if a member wants to learn to program using an unused old robot, let them. I am proof at what one can learn form messing with an old robot.
3. When in doubt, always throttle down while loops.
4. Never assume when you cand test and find out.
5. no matter wh0 has more points, the watchdog always wins.
6. If your team uses dropbox or the like, always back up your most recent code revisions alongside codes for old robots. You never know when you might want to take a look at it...
7. Never be afraid to ask "noob" questions if they are serious...
__________________
Dean's List Semi-finalist 2010
1747 Harrison Boiler Robotics 2008-2010, 2783 Engineers of Tomorrow 2011, Event Volunteer 2012-current

DISCLAIMER: Any opinions/comments posted are solely my personal opinion and does not reflect the views/opinions of FIRST, IndianaFIRST, or any other organization.
Reply With Quote