Silly Programming screw ups (funny)

[tdlrali]

I instituted a policy of "defensive programming" a couple of years ago. Simple, easy-to-understand subroutines that provided simple, easy-to-understand feedback to show the state of sensors and their desired operation. The electrical/mechanical group quickly comes to trust the software group when a wiring problem can be identified by the lack of a light or a non-incrementing number.

Yeah, same here. Our terminal can display almost any input and output of the RC, so when they tell me that I need to fix something, I just show them that the input is not correct or that the output is correct.