"It mustbe ahardwareproblem.""THIScan't bethe sourceof THAT.""Must bea networkissues.""Somebodymust havechangedmy code.""You can'tuse thatversion onyoursystem.""Why doyou wantto do itthat way?""I haven'ttouched thatmodule inweeks!""Must beadatabaseissue.""But all ofmy unittestspassed""You musthave thewrongversion."It workson mymachine.""It workedinSTAGING.""Buildserver isdown.""It's justsomeunluckycoincidence.""There issomethingfunky inyour data.""Can weget Coryon that.""Even thoughit doesn'twork, howdoes it feel?"What didyou type inwrong to getit to crash?""We willbe out by7:30p.""Did youcheck for avirus on yoursystem?""I think it'sthe LoadBalancer.""We didn'tmake anychanges inthat area.""Where wereyou whenthe programblew up?""Isn'tthat IT'sjob?""It mustbe ahardwareproblem.""THIScan't bethe sourceof THAT.""Must bea networkissues.""Somebodymust havechangedmy code.""You can'tuse thatversion onyoursystem.""Why doyou wantto do itthat way?""I haven'ttouched thatmodule inweeks!""Must beadatabaseissue.""But all ofmy unittestspassed""You musthave thewrongversion."It workson mymachine.""It workedinSTAGING.""Buildserver isdown.""It's justsomeunluckycoincidence.""There issomethingfunky inyour data.""Can weget Coryon that.""Even thoughit doesn'twork, howdoes it feel?"What didyou type inwrong to getit to crash?""We willbe out by7:30p.""Did youcheck for avirus on yoursystem?""I think it'sthe LoadBalancer.""We didn'tmake anychanges inthat area.""Where wereyou whenthe programblew up?""Isn'tthat IT'sjob?"

Software Engineer Bingo 04/21/2014 - Call List

(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.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. "It must be a hardware problem."
  2. "THIS can't be the source of THAT."
  3. "Must be a network issues."
  4. "Somebody must have changed my code."
  5. "You can't use that version on your system."
  6. "Why do you want to do it that way?"
  7. "I haven't touched that module in weeks!"
  8. "Must be a database issue."
  9. "But all of my unit tests passed"
  10. "You must have the wrong version."
  11. It works on my machine."
  12. "It worked in STAGING."
  13. "Build server is down."
  14. "It's just some unlucky coincidence."
  15. "There is something funky in your data."
  16. "Can we get Cory on that."
  17. "Even though it doesn't work, how does it feel?
  18. "What did you type in wrong to get it to crash?"
  19. "We will be out by 7:30p."
  20. "Did you check for a virus on your system?"
  21. "I think it's the Load Balancer."
  22. "We didn't make any changes in that area."
  23. "Where were you when the program blew up?"
  24. "Isn't that IT's job?"