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