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

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