on-sitefolk bragaboutfood“whatcould gowrong?”“we’relookinginto this”ping indog-critical-issuesA sitegoesdown“we’realmostthere”office coldenoughfor coatsbusfundissuesmajorincident inoff hoursping pongball rollsinto devroomsomethingnewcompletelybreaks“itworkedlocally”> 3people atonecomputerleaderboardoutagessomeonegroansloudly outof nowhereOfflinedonationissuePM inthe devroommaybeit’scaching?@here or@channelCSChamp inthe devroomsomeoneswearsout ofnowherevendorstatusincidentsearchweirdnessan old bugresurfacessomeonegets acallDonationsnotworkingdogdeployon-site folkmentionhow crazyit issomethinglive notwhat theyexpectedslack calllongerthan 1hrfinding anewworkaroundweb/apideploystats“wrong”feedramaleaderboards“wrong”Statsnotupdatingp2pissuescustomerloveunrelated toatxcustomerloverelated to atxon-sitefolk bragaboutfood“whatcould gowrong?”“we’relookinginto this”ping indog-critical-issuesA sitegoesdown“we’realmostthere”office coldenoughfor coatsbusfundissuesmajorincident inoff hoursping pongball rollsinto devroomsomethingnewcompletelybreaks“itworkedlocally”> 3people atonecomputerleaderboardoutagessomeonegroansloudly outof nowhereOfflinedonationissuePM inthe devroommaybeit’scaching?@here or@channelCSChamp inthe devroomsomeoneswearsout ofnowherevendorstatusincidentsearchweirdnessan old bugresurfacessomeonegets acallDonationsnotworkingdogdeployon-site folkmentionhow crazyit issomethinglive notwhat theyexpectedslack calllongerthan 1hrfinding anewworkaroundweb/apideploystats“wrong”feedramaleaderboards“wrong”Statsnotupdatingp2pissuescustomerloveunrelated toatxcustomerloverelated to atx

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