View Single Post
  #7   Spotlight this post!  
Unread 22-02-2012, 10:27
~Cory~'s Avatar
~Cory~ ~Cory~ is offline
Student
AKA: Cory Rypkema
FRC #0706
Team Role: Alumni
 
Join Date: Jan 2010
Rookie Year: 2010
Location: Worcester MA
Posts: 216
~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold
Re: Things Learned During Build Season

As a programmer I learned that ~90% of all problems can be solved with this process: (Rather than guess/check or theoretical fixes)

1. Ping the Robot
2. Check the voltage (under load!!!)
3. Check and keep your documentation ACCURATE
4. Walk through your logic with sample data. Then have someone else walk through a psuedocode version. Numbers should match
5. If something works, save and create a backup
6. Sockets, Threading and Vision can be difficult. Split the work up
7. Use the debugger. Its there for a reason.
8. Read the output from netconsole or serial during startup. You can find many hidden errors there, such as defaulting to old code!
__________________
corin.rypkema.org
WPI Class of '17
'12 Dean's List Finalist, Mentor of 706 - Cyberhawks
Reply With Quote