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

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