manuallyupdatingpostgres"How didthis workin the firstplace..."issueswith PGBosscannotupdateconfiginstancediesissueswithIIMpeakperformanceshipit!failureswithfingerprintworkerdiesgatewayerrorsneed toredesignfeaturecommentson John'semojis"It wasn'tmy fault..."postgrescrashescannotuploaddriverssomeoneunfamiliarwith oldfeatureslate tostarttestingsomeoneasks howto get logs"Iswear I..."confusionwithHIPAAaccidentallydroppingthedatabaseissueswithhivecomplainaboutinfrastructuremanuallyupdatingpostgres"How didthis workin the firstplace..."issueswith PGBosscannotupdateconfiginstancediesissueswithIIMpeakperformanceshipit!failureswithfingerprintworkerdiesgatewayerrorsneed toredesignfeaturecommentson John'semojis"It wasn'tmy fault..."postgrescrashescannotuploaddriverssomeoneunfamiliarwith oldfeatureslate tostarttestingsomeoneasks howto get logs"Iswear I..."confusionwithHIPAAaccidentallydroppingthedatabaseissueswithhivecomplainaboutinfrastructure

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