commentson John'semojis"Iswear I...""How didthis workin the firstplace..."someoneasks howto get logscomplainaboutinfrastructureissueswithhivesomeoneunfamiliarwith oldfeaturescannotupdateconfigpeakperformancepostgrescrashesneed toredesignfeatureconfusionwithHIPAAworkerdiesissueswithIIMaccidentallydroppingthedatabase"It wasn'tmy fault..."issueswith PGBossmanuallyupdatingpostgreslate tostarttestingcannotuploaddriversshipit!failureswithfingerprintinstancediesgatewayerrorscommentson John'semojis"Iswear I...""How didthis workin the firstplace..."someoneasks howto get logscomplainaboutinfrastructureissueswithhivesomeoneunfamiliarwith oldfeaturescannotupdateconfigpeakperformancepostgrescrashesneed toredesignfeatureconfusionwithHIPAAworkerdiesissueswithIIMaccidentallydroppingthedatabase"It wasn'tmy fault..."issueswith PGBossmanuallyupdatingpostgreslate tostarttestingcannotuploaddriversshipit!failureswithfingerprintinstancediesgatewayerrors

Test Event #2 - 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. comments on John's emojis
  2. "I swear I ..."
  3. "How did this work in the first place..."
  4. someone asks how to get logs
  5. complain about infrastructure
  6. issues with hive
  7. someone unfamiliar with old features
  8. cannot update config
  9. peak performance
  10. postgres crashes
  11. need to redesign feature
  12. confusion with HIPAA
  13. worker dies
  14. issues with IIM
  15. accidentally dropping the database
  16. "It wasn't my fault ..."
  17. issues with PG Boss
  18. manually updating postgres
  19. late to start testing
  20. cannot upload drivers
  21. ship it!
  22. failures with fingerprint
  23. instance dies
  24. gateway errors