"Theyshouldreach out tohelpdesk""It's justsome unluckycoincidence.""Somebodymust havechangedmy code.""There'sno waythat's theproblem""There issomethingfunky inyour data.""My testspassedlocally...""It works,but it hasn'tbeentested.""Must beadatabaseissue.""I can't testeverything!""Must bea networkissue.""It mustbe aserverproblem.""It workson mymachine.""It's neverdone thatbefore.""That'sweird...""How isthatpossible?""I haven'ttouchedthat codein weeks!""The usermust havedonesomethingwrong"Committeddirectly tomain"You musthave thewrongversion.""It workedyesterday.""You can'tuse thatversion onyoursystem.""Have youtriedrestarting?"Writtencode thattook downproduction"Eventhough itdoesn't work,how does itlook?"Theyshouldreach out tohelpdesk""It's justsome unluckycoincidence.""Somebodymust havechangedmy code.""There'sno waythat's theproblem""There issomethingfunky inyour data.""My testspassedlocally...""It works,but it hasn'tbeentested.""Must beadatabaseissue.""I can't testeverything!""Must bea networkissue.""It mustbe aserverproblem.""It workson mymachine.""It's neverdone thatbefore.""That'sweird...""How isthatpossible?""I haven'ttouchedthat codein weeks!""The usermust havedonesomethingwrong"Committeddirectly tomain"You musthave thewrongversion.""It workedyesterday.""You can'tuse thatversion onyoursystem.""Have youtriedrestarting?"Writtencode thattook downproduction"Eventhough itdoesn't work,how does itlook?

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. "They should reach out to helpdesk"
  2. "It's just some unlucky coincidence."
  3. "Somebody must have changed my code."
  4. "There's no way that's the problem"
  5. "There is something funky in your data."
  6. "My tests passed locally..."
  7. "It works, but it hasn't been tested."
  8. "Must be a database issue."
  9. "I can't test everything!"
  10. "Must be a network issue."
  11. "It must be a server problem."
  12. "It works on my machine."
  13. "It's never done that before."
  14. "That's weird..."
  15. "How is that possible?"
  16. "I haven't touched that code in weeks!"
  17. "The user must have done something wrong"
  18. Committed directly to main
  19. "You must have the wrong version."
  20. "It worked yesterday."
  21. "You can't use that version on your system."
  22. "Have you tried restarting?"
  23. Written code that took down production
  24. "Even though it doesn't work, how does it look?