issueswithIIMsomeoneasks howto get logsfailureswithfingerprintconfusionwithHIPAAcannotuploaddriverssomeoneunfamiliarwith oldfeaturespostgrescrashespeakperformanceneed toredesignfeaturecommentson John'semojisissueswithhive"It wasn'tmy fault..."manuallyupdatingpostgres"How didthis workin the firstplace..."workerdiescannotupdateconfig"Iswear I..."gatewayerrorsissueswith PGBosslate tostarttestinginstancediescomplainaboutinfrastructureaccidentallydroppingthedatabaseshipit!issueswithIIMsomeoneasks howto get logsfailureswithfingerprintconfusionwithHIPAAcannotuploaddriverssomeoneunfamiliarwith oldfeaturespostgrescrashespeakperformanceneed toredesignfeaturecommentson John'semojisissueswithhive"It wasn'tmy fault..."manuallyupdatingpostgres"How didthis workin the firstplace..."workerdiescannotupdateconfig"Iswear I..."gatewayerrorsissueswith PGBosslate tostarttestinginstancediescomplainaboutinfrastructureaccidentallydroppingthedatabaseshipit!

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