"Must be a network issue." "It works on my machine." "You can't use that version on your system." "Did you check for a virus on your system?" "It must be a hardware problem." "You must have the wrong version." "Somebody must have changed my code." "THIS can't be the source of THAT." "How is that possible?" "I can't test everything!" "Where were you when the program blew up?" "It works, but it hasn't been tested." "Isn't that IT's job?" "It's just some unlucky coincidence." "It worked yesterday." "What did you type in wrong to get it to crash?" "Why do you want to do it that way?" "Must be a database issue." "Even though it doesn't work, how does it look? "It's never done that before." "I haven't touched that module in weeks!" "There is something funky in your data." "It worked in STAGING." "That's weird..." "Must be a network issue." "It works on my machine." "You can't use that version on your system." "Did you check for a virus on your system?" "It must be a hardware problem." "You must have the wrong version." "Somebody must have changed my code." "THIS can't be the source of THAT." "How is that possible?" "I can't test everything!" "Where were you when the program blew up?" "It works, but it hasn't been tested." "Isn't that IT's job?" "It's just some unlucky coincidence." "It worked yesterday." "What did you type in wrong to get it to crash?" "Why do you want to do it that way?" "Must be a database issue." "Even though it doesn't work, how does it look? "It's never done that before." "I haven't touched that module in weeks!" "There is something funky in your data." "It worked in STAGING." "That's weird..."
(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.
"Must be a network issue."
"It works on my machine."
"You can't use that version on your system."
"Did you check for a virus on your system?"
"It must be a hardware problem."
"You must have the wrong version."
"Somebody must have changed my code."
"THIS can't be the source of THAT."
"How is that possible?"
"I can't test everything!"
"Where were you when the program blew up?"
"It works, but it hasn't been tested."
"Isn't that IT's job?"
"It's just some unlucky coincidence."
"It worked yesterday."
"What did you type in wrong to get it to crash?"
"Why do you want to do it that way?"
"Must be a database issue."
"Even though it doesn't work, how does it look?
"It's never done that before."
"I haven't touched that module in weeks!"
"There is something funky in your data."
"It worked in STAGING."
"That's weird..."