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

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