"There is something funky in your data." "It must be a hardware problem." "We will be out by 7:30p." "Somebody must have changed my code." "Must be a network issues." "Even though it doesn't work, how does it feel? "It worked in STAGING." "THIS can't be the source of THAT." "But all of my unit tests passed" "I think it's the Load Balancer." "What did you type in wrong to get it to crash?" "You can't use that version on your system." "Isn't that IT's job?" "You must have the wrong version." "We didn't make any changes in that area." "Why do you want to do it that way?" "It's just some unlucky coincidence." "Build server is down." It works on my machine." "Did you check for a virus on your system?" "I haven't touched that module in weeks!" "Must be a database issue." "Where were you when the program blew up?" "Can we get Cory on that." "There is something funky in your data." "It must be a hardware problem." "We will be out by 7:30p." "Somebody must have changed my code." "Must be a network issues." "Even though it doesn't work, how does it feel? "It worked in STAGING." "THIS can't be the source of THAT." "But all of my unit tests passed" "I think it's the Load Balancer." "What did you type in wrong to get it to crash?" "You can't use that version on your system." "Isn't that IT's job?" "You must have the wrong version." "We didn't make any changes in that area." "Why do you want to do it that way?" "It's just some unlucky coincidence." "Build server is down." It works on my machine." "Did you check for a virus on your system?" "I haven't touched that module in weeks!" "Must be a database issue." "Where were you when the program blew up?" "Can we get Cory on that."
(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.
"There is something funky in your data."
"It must be a hardware problem."
"We will be out by 7:30p."
"Somebody must have changed my code."
"Must be a network issues."
"Even though it doesn't work, how does it feel?
"It worked in STAGING."
"THIS can't be the source of THAT."
"But all of my unit tests passed"
"I think it's the Load Balancer."
"What did you type in wrong to get it to crash?"
"You can't use that version on your system."
"Isn't that IT's job?"
"You must have the wrong version."
"We didn't make any changes in that area."
"Why do you want to do it that way?"
"It's just some unlucky coincidence."
"Build server is down."
It works on my machine."
"Did you check for a virus on your system?"
"I haven't touched that module in weeks!"
"Must be a database issue."
"Where were you when the program blew up?"
"Can we get Cory on that."