late tostarttestingcommentson John'semojisconfusionwithHIPAAinstancedies"How didthis workin the firstplace..."issueswith PGBosspostgrescrashes"It wasn'tmy fault..."complainaboutinfrastructurecannotupdateconfigissueswithIIMgatewayerrorsworkerdiesshipit!need toredesignfeaturepeakperformancecannotuploaddriverssomeoneunfamiliarwith oldfeaturesmanuallyupdatingpostgresaccidentallydroppingthedatabasefailureswithfingerprintsomeoneasks howto get logsissueswithhive"Iswear I..."late tostarttestingcommentson John'semojisconfusionwithHIPAAinstancedies"How didthis workin the firstplace..."issueswith PGBosspostgrescrashes"It wasn'tmy fault..."complainaboutinfrastructurecannotupdateconfigissueswithIIMgatewayerrorsworkerdiesshipit!need toredesignfeaturepeakperformancecannotuploaddriverssomeoneunfamiliarwith oldfeaturesmanuallyupdatingpostgresaccidentallydroppingthedatabasefailureswithfingerprintsomeoneasks howto get logsissueswithhive"Iswear I..."

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