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

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