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

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