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

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