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

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