cannotupdateconfigcannotuploaddriverssomeoneasks howto get logs"How didthis workin the firstplace..."someoneunfamiliarwith oldfeaturesmanuallyupdatingpostgreslate tostarttestingconfusionwithHIPAA"Iswear I..."accidentallydroppingthedatabaseneed toredesignfeatureissueswithIIMpostgrescrashesgatewayerrorsshipit!commentson John'semojiscomplainaboutinfrastructureinstancediespeakperformanceissueswith PGBossworkerdies"It wasn'tmy fault..."issueswithhivefailureswithfingerprintcannotupdateconfigcannotuploaddriverssomeoneasks howto get logs"How didthis workin the firstplace..."someoneunfamiliarwith oldfeaturesmanuallyupdatingpostgreslate tostarttestingconfusionwithHIPAA"Iswear I..."accidentallydroppingthedatabaseneed toredesignfeatureissueswithIIMpostgrescrashesgatewayerrorsshipit!commentson John'semojiscomplainaboutinfrastructureinstancediespeakperformanceissueswith PGBossworkerdies"It wasn'tmy fault..."issueswithhivefailureswithfingerprint

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