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