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

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