kwolfskill
Well-Known Member
For me, it is wanting to know what something will do, before it gets used. Accidents happen, and as long as there is an RTH button on the controller, it can get pressed at some point. I don't want to wait until that point to find out what it is going to do.
Maybe I let someone else handle the controller for a moment. Maybe I dropped the controller and the RTH button got pressed when the controller hit the ground. Maybe I just wasn't paying attention and hit the RTH button when moving my fingers. In any case, as long as it exists, it can get pressed.
As a Director of Software Delivery, I require my developers to test every single code path. If they put a button on a screen, they need to know, and validate, what happens when that button gets pressed. If that button acts differently under different scenarios, then they need to test all of those scenarios.
"Should" that button need be pressed is different than "can" that button get pressed.
Maybe I let someone else handle the controller for a moment. Maybe I dropped the controller and the RTH button got pressed when the controller hit the ground. Maybe I just wasn't paying attention and hit the RTH button when moving my fingers. In any case, as long as it exists, it can get pressed.
As a Director of Software Delivery, I require my developers to test every single code path. If they put a button on a screen, they need to know, and validate, what happens when that button gets pressed. If that button acts differently under different scenarios, then they need to test all of those scenarios.
"Should" that button need be pressed is different than "can" that button get pressed.