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