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