Software developer is assigned the task of chasing down a bug that involves a true-or-false value that’s not right, says a pilot fish on the scene.

“A boolean variable wasn’t receiving the correct value at some point before being evaluated in an if statement,” fish says. “The developer started by checking the use cases where the boolean was supposed to be false.

“After spending some time on it, he still wasn’t able to determine what caused the boolean to have the wrong value.

“Then he had a brilliant idea: simply assign the ‘false’ value to the boolean just before the if statement. And boom! It worked!

“He declared the bug fixed and it went to the tester — who pointed out the obvious fact that the application was not working properly when that boolean was supposed to be true.

To read this article in full, please click here