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

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