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

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