Quote:
Originally Posted by Andrew Schreiber
Thems fighting words Chris.
No, really the reason is because programming is not always understood. My standard debugging practice: Reproduce the error 2 times in the pit, mech/elec check sensors/motors while prog checks the code for those inputs.
Programmers, the LAST thing you should do is say it isn't the code.
|
I've said a few times that I was
sure the problem wasn't the code. Every time, it turned out not to be in the code. A programmer should at least be able to tell if something definitely ISN'T a code issue, when it definitely IS a code issue, and when he should keep quiet because the cause isn't certain.