confusionwithHIPAAworkerdiescomplainaboutinfrastructuresomeoneasks howto get logscannotuploaddriversissueswith PGBosslate tostarttestinggatewayerrors"Iswear I...""It wasn'tmy fault..."need toredesignfeaturemanuallyupdatingpostgrescannotupdateconfigfailureswithfingerprintpeakperformanceissueswithhiveissueswithIIMaccidentallydroppingthedatabaseshipit!someoneunfamiliarwith oldfeaturespostgrescrashes"How didthis workin the firstplace..."commentson John'semojisinstancediesconfusionwithHIPAAworkerdiescomplainaboutinfrastructuresomeoneasks howto get logscannotuploaddriversissueswith PGBosslate tostarttestinggatewayerrors"Iswear I...""It wasn'tmy fault..."need toredesignfeaturemanuallyupdatingpostgrescannotupdateconfigfailureswithfingerprintpeakperformanceissueswithhiveissueswithIIMaccidentallydroppingthedatabaseshipit!someoneunfamiliarwith oldfeaturespostgrescrashes"How didthis workin the firstplace..."commentson John'semojisinstancedies

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