workerdieslate tostarttestingmanuallyupdatingpostgresgatewayerrorscommentson John'semojisinstancedies"It wasn'tmy fault..."someoneunfamiliarwith oldfeaturespostgrescrashesissueswithIIMfailureswithfingerprintcannotupdateconfigshipit!"How didthis workin the firstplace..."cannotuploaddriversaccidentallydroppingthedatabaseneed toredesignfeatureissueswithhive"Iswear I..."someoneasks howto get logsissueswith PGBosspeakperformanceconfusionwithHIPAAcomplainaboutinfrastructureworkerdieslate tostarttestingmanuallyupdatingpostgresgatewayerrorscommentson John'semojisinstancedies"It wasn'tmy fault..."someoneunfamiliarwith oldfeaturespostgrescrashesissueswithIIMfailureswithfingerprintcannotupdateconfigshipit!"How didthis workin the firstplace..."cannotuploaddriversaccidentallydroppingthedatabaseneed toredesignfeatureissueswithhive"Iswear I..."someoneasks howto get logsissueswith PGBosspeakperformanceconfusionwithHIPAAcomplainaboutinfrastructure

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