"I can't testeverything!""It mustbe ahardwareproblem.""It's justsomeunluckycoincidence.""Did youcheck for avirus on yoursystem?""I haven'ttouched thatmodule inweeks!""Where wereyou whenthe programblew up?""It workson mymachine.""What didyou type inwrong to getit to crash?""Why doyou wantto do itthat way?""That'sweird...""It workedyesterday.""It works,but it hasn'tbeentested.""You musthave thewrongversion.""THIScan't bethe sourceof THAT.""Even thoughit doesn'twork, howdoes it feel?"Must beadatabaseissue.""How isthatpossible?""Somebodymust havechangedmy code.""Must bea networkissues.""Isn'tthat IT'sjob?""You can'tuse thatversion onyoursystem.""There issomethingfunky inyour data.""It workedinSTAGING.""It's neverdone thatbefore.""I can't testeverything!""It mustbe ahardwareproblem.""It's justsomeunluckycoincidence.""Did youcheck for avirus on yoursystem?""I haven'ttouched thatmodule inweeks!""Where wereyou whenthe programblew up?""It workson mymachine.""What didyou type inwrong to getit to crash?""Why doyou wantto do itthat way?""That'sweird...""It workedyesterday.""It works,but it hasn'tbeentested.""You musthave thewrongversion.""THIScan't bethe sourceof THAT.""Even thoughit doesn'twork, howdoes it feel?"Must beadatabaseissue.""How isthatpossible?""Somebodymust havechangedmy code.""Must bea networkissues.""Isn'tthat IT'sjob?""You can'tuse thatversion onyoursystem.""There issomethingfunky inyour data.""It workedinSTAGING.""It's neverdone thatbefore."

Software Engineer Bingo - 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. "I can't test everything!"
  2. "It must be a hardware problem."
  3. "It's just some unlucky coincidence."
  4. "Did you check for a virus on your system?"
  5. "I haven't touched that module in weeks!"
  6. "Where were you when the program blew up?"
  7. "It works on my machine."
  8. "What did you type in wrong to get it to crash?"
  9. "Why do you want to do it that way?"
  10. "That's weird..."
  11. "It worked yesterday."
  12. "It works, but it hasn't been tested."
  13. "You must have the wrong version."
  14. "THIS can't be the source of THAT."
  15. "Even though it doesn't work, how does it feel?
  16. "Must be a database issue."
  17. "How is that possible?"
  18. "Somebody must have changed my code."
  19. "Must be a network issues."
  20. "Isn't that IT's job?"
  21. "You can't use that version on your system."
  22. "There is something funky in your data."
  23. "It worked in STAGING."
  24. "It's never done that before."