accidentallydroppingthedatabasecommentson John'semojisneed toredesignfeaturesomeoneunfamiliarwith oldfeaturesgatewayerrors"Iswear I..."confusionwithHIPAAissueswithIIMfailureswithfingerprintissueswith PGBosspeakperformance"It wasn'tmy fault..."issueswithhivesomeoneasks howto get logsshipit!complainaboutinfrastructurelate tostarttestingcannotuploaddriverscannotupdateconfigmanuallyupdatingpostgresworkerdiespostgrescrashesinstancedies"How didthis workin the firstplace..."accidentallydroppingthedatabasecommentson John'semojisneed toredesignfeaturesomeoneunfamiliarwith oldfeaturesgatewayerrors"Iswear I..."confusionwithHIPAAissueswithIIMfailureswithfingerprintissueswith PGBosspeakperformance"It wasn'tmy fault..."issueswithhivesomeoneasks howto get logsshipit!complainaboutinfrastructurelate tostarttestingcannotuploaddriverscannotupdateconfigmanuallyupdatingpostgresworkerdiespostgrescrashesinstancedies"How didthis workin the firstplace..."

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