View Single Post
  #43   Spotlight this post!  
Unread 04-04-2010, 12:41
kgzak's Avatar
kgzak kgzak is offline
Registered User
AKA: Kris
FRC #4392 (Decievers) FRC #2075 (Enigma)
Team Role: College Student
 
Join Date: Dec 2008
Rookie Year: 2008
Location: Grand Rapids, Michigan
Posts: 418
kgzak is a splendid one to beholdkgzak is a splendid one to beholdkgzak is a splendid one to beholdkgzak is a splendid one to beholdkgzak is a splendid one to beholdkgzak is a splendid one to beholdkgzak is a splendid one to behold
Re: why blame the programmers??

Quote:
Originally Posted by synth3tk View Post
Because most often, it is the programmer's fault.
Quote:
Originally Posted by AmoryG View Post
Because if hardware broke as easy as code does, no team could afford to build a robot. If we were playing a match and suddenly our robot did something it was not supposed to, I would suspect that either the code or a sensor was not working as it should. Code breaks easy, and if our robot suddenly started malfunctioning, I would load up the most basic code that works beyond a doubt to confirm whether it was us programmers we should have blamed.
Most of the time, on our team, it was the hardware. Our main code wise was motors running backwards, but that was because a day before competition the build team decided to turn the motors 180 degrees. We also had watchdog errors, but that was because our WGA was bad. I don't remember any other problems with code/electrical.