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

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