A sitegoesdownsomeonegets acallvendorstatusincidentsomethingnewcompletelybreaksStatsnotupdatingfinding anewworkaroundan old bugresurfacescustomerloveunrelated toatxDonationsnotworkingsearchweirdnesson-site folkmentionhow crazyit ismaybeit’scaching?leaderboards“wrong”PM inthe devroomcustomerloverelated to atxp2pissuesoffice coldenoughfor coatsslack calllongerthan 1hrping indog-critical-issuesmajorincident inoff hoursOfflinedonationissue“we’realmostthere”web/apideploy“itworkedlocally”CSChamp inthe devroomstats“wrong”on-sitefolk bragaboutfood“whatcould gowrong?”“we’relookinginto this”ping pongball rollsinto devroom@here or@channelsomeonegroansloudly outof nowherefeedramaleaderboardoutagesdogdeploysomeoneswearsout ofnowherebusfundissuessomethinglive notwhat theyexpected> 3people atonecomputerA sitegoesdownsomeonegets acallvendorstatusincidentsomethingnewcompletelybreaksStatsnotupdatingfinding anewworkaroundan old bugresurfacescustomerloveunrelated toatxDonationsnotworkingsearchweirdnesson-site folkmentionhow crazyit ismaybeit’scaching?leaderboards“wrong”PM inthe devroomcustomerloverelated to atxp2pissuesoffice coldenoughfor coatsslack calllongerthan 1hrping indog-critical-issuesmajorincident inoff hoursOfflinedonationissue“we’realmostthere”web/apideploy“itworkedlocally”CSChamp inthe devroomstats“wrong”on-sitefolk bragaboutfood“whatcould gowrong?”“we’relookinginto this”ping pongball rollsinto devroom@here or@channelsomeonegroansloudly outof nowherefeedramaleaderboardoutagesdogdeploysomeoneswearsout ofnowherebusfundissuessomethinglive notwhat theyexpected> 3people atonecomputer

Amplify - 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
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
  1. A site goes down
  2. someone gets a call
  3. vendor status incident
  4. something new completely breaks
  5. Stats not updating
  6. finding a new workaround
  7. an old bug resurfaces
  8. customerlove unrelated to atx
  9. Donations not working
  10. search weirdness
  11. on-site folk mention how crazy it is
  12. maybe it’s caching?
  13. leaderboards “wrong”
  14. PM in the dev room
  15. customerlove related to atx
  16. p2p issues
  17. office cold enough for coats
  18. slack call longer than 1hr
  19. ping in dog-critical-issues
  20. major incident in off hours
  21. Offline donation issue
  22. “we’re almost there”
  23. web/api deploy
  24. “it worked locally”
  25. CS Champ in the dev room
  26. stats “wrong”
  27. on-site folk brag about food
  28. “what could go wrong?”
  29. “we’re looking into this”
  30. ping pong ball rolls into dev room
  31. @here or @channel
  32. someone groans loudly out of nowhere
  33. fee drama
  34. leaderboard outages
  35. dog deploy
  36. someone swears out of nowhere
  37. bus fund issues
  38. something live not what they expected
  39. > 3 people at one computer