"Why doyou wantto do itthat way?""It workedinSTAGING.""What didyou type inwrong to getit to crash?""Buildserver isdown.""We willbe out by7:30p.""But all ofmy unittestspassed""Must bea networkissues.""Somebodymust havechangedmy code.""Isn'tthat IT'sjob?""It mustbe ahardwareproblem.""We didn'tmake anychanges inthat area.""I think it'sthe LoadBalancer.""You musthave thewrongversion.""Must beadatabaseissue.""It's justsomeunluckycoincidence.""Did youcheck for avirus on yoursystem?"It workson mymachine.""I haven'ttouched thatmodule inweeks!""There issomethingfunky inyour data.""You can'tuse thatversion onyoursystem.""Even thoughit doesn'twork, howdoes it feel?"Where wereyou whenthe programblew up?""Can weget Coryon that.""THIScan't bethe sourceof THAT.""Why doyou wantto do itthat way?""It workedinSTAGING.""What didyou type inwrong to getit to crash?""Buildserver isdown.""We willbe out by7:30p.""But all ofmy unittestspassed""Must bea networkissues.""Somebodymust havechangedmy code.""Isn'tthat IT'sjob?""It mustbe ahardwareproblem.""We didn'tmake anychanges inthat area.""I think it'sthe LoadBalancer.""You musthave thewrongversion.""Must beadatabaseissue.""It's justsomeunluckycoincidence.""Did youcheck for avirus on yoursystem?"It workson mymachine.""I haven'ttouched thatmodule inweeks!""There issomethingfunky inyour data.""You can'tuse thatversion onyoursystem.""Even thoughit doesn'twork, howdoes it feel?"Where wereyou whenthe programblew up?""Can weget Coryon that.""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. "Why do you want to do it that way?"
  2. "It worked in STAGING."
  3. "What did you type in wrong to get it to crash?"
  4. "Build server is down."
  5. "We will be out by 7:30p."
  6. "But all of my unit tests passed"
  7. "Must be a network issues."
  8. "Somebody must have changed my code."
  9. "Isn't that IT's job?"
  10. "It must be a hardware problem."
  11. "We didn't make any changes in that area."
  12. "I think it's the Load Balancer."
  13. "You must have the wrong version."
  14. "Must be a database issue."
  15. "It's just some unlucky coincidence."
  16. "Did you check for a virus on your system?"
  17. It works on my machine."
  18. "I haven't touched that module in weeks!"
  19. "There is something funky in your data."
  20. "You can't use that version on your system."
  21. "Even though it doesn't work, how does it feel?
  22. "Where were you when the program blew up?"
  23. "Can we get Cory on that."
  24. "THIS can't be the source of THAT."