"There's no way that's the problem" Committed directly to main "I can't test everything!" "The user must have done something wrong" "They should reach out to helpdesk" Written code that took down production "There is something funky in your data." "You can't use that version on your system." "That's weird..." "It works, but it hasn't been tested." "Have you tried restarting?" "How is that possible?" "Somebody must have changed my code." "It worked yesterday." "You must have the wrong version." "Must be a network issue." "It must be a server problem." "It's just some unlucky coincidence." "I haven't touched that code in weeks!" "It's never done that before." "My tests passed locally..." "Must be a database issue." "Even though it doesn't work, how does it look? "It works on my machine." "There's no way that's the problem" Committed directly to main "I can't test everything!" "The user must have done something wrong" "They should reach out to helpdesk" Written code that took down production "There is something funky in your data." "You can't use that version on your system." "That's weird..." "It works, but it hasn't been tested." "Have you tried restarting?" "How is that possible?" "Somebody must have changed my code." "It worked yesterday." "You must have the wrong version." "Must be a network issue." "It must be a server problem." "It's just some unlucky coincidence." "I haven't touched that code in weeks!" "It's never done that before." "My tests passed locally..." "Must be a database issue." "Even though it doesn't work, how does it look? "It works on my machine."
(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's no way that's the problem"
Committed directly to main
"I can't test everything!"
"The user must have done something wrong"
"They should reach out to helpdesk"
Written code that took down production
"There is something funky in your data."
"You can't use that version on your system."
"That's weird..."
"It works, but it hasn't been tested."
"Have you tried restarting?"
"How is that possible?"
"Somebody must have changed my code."
"It worked yesterday."
"You must have the wrong version."
"Must be a network issue."
"It must be a server problem."
"It's just some unlucky coincidence."
"I haven't touched that code in weeks!"
"It's never done that before."
"My tests passed locally..."
"Must be a database issue."
"Even though it doesn't work, how does it look?
"It works on my machine."