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

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