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

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