Quote:
Originally Posted by synth3tk
Because most often, it is the programmer's fault.
|
I'm sorry our program cannot handle hardware failure as well as you would like. I'm sorry it can't detect that the kicker hit & broke the drive encoder. I'm sorry it can't detect that the latch is broken (as in holds, but for less than 1 sec) and that the loader arm needs to stay extended.
In seriousness though, it programming's fault 3 times.
1) I accidentally commented out `break;' in a series of 1-line cases. (dumb---- attack)
2) Andrew accidentally commented out `break;' in a (different) series of 1-line cases. (legit reason, was making changes on the fly at comp.)
3) We had a ``real'' bug. The code worked most the time, but failed to handle a fringe-case with censor input. I wish I could remember exactly what it was. I wrote this part of the code
stipulation: If a hardware change is made that necessitates a code change, but the programmers are not informed of this, it is not programming's fault.
stipulation: If the programmers were not correctly informed of what the code should make the hardware do, yes you can maybe blame programming a bit. But it is not a `code problem'.
The code is perfect. It does what we tell it to. Any incorrect behavior is because we told it to do the wrong thing. We have 2 exceptions to this.
If we told the code to do the wrong thing it is probably because physical told us the wrong thing. We have one exception to this.
Quote:
Originally Posted by AmoryG
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.
|
Yes, but:
1) we haven't changed the code since yesterday, when it was working.
2) when we did change the code before that, it had nothing to do with what broke
3) no, there is no chance that it no longer has code on it. It went out and ran, didn't it?
Therefore, the sensor broke, the wire came out, or you burnt out the motor.