slack calllongerthan 1hroffice coldenoughfor coatsfinding anewworkaroundping pongball rollsinto devroomcustomerloveunrelated toatxbusfundissuesPM inthe devroom> 3people atonecomputerp2pissuesmajorincident inoff hours“whatcould gowrong?”leaderboardoutages“we’relookinginto this”customerloverelated to atxStatsnotupdating@here or@channelstats“wrong”on-sitefolk bragaboutfoodleaderboards“wrong”feedramaan old bugresurfacesA sitegoesdown“we’realmostthere”maybeit’scaching?web/apideploysearchweirdness“itworkedlocally”CSChamp inthe devroomdogdeployvendorstatusincidentsomethinglive notwhat theyexpectedsomeonegroansloudly outof nowheresomeoneswearsout ofnowhereon-site folkmentionhow crazyit isOfflinedonationissueping indog-critical-issuesDonationsnotworkingsomeonegets acallsomethingnewcompletelybreaksslack calllongerthan 1hroffice coldenoughfor coatsfinding anewworkaroundping pongball rollsinto devroomcustomerloveunrelated toatxbusfundissuesPM inthe devroom> 3people atonecomputerp2pissuesmajorincident inoff hours“whatcould gowrong?”leaderboardoutages“we’relookinginto this”customerloverelated to atxStatsnotupdating@here or@channelstats“wrong”on-sitefolk bragaboutfoodleaderboards“wrong”feedramaan old bugresurfacesA sitegoesdown“we’realmostthere”maybeit’scaching?web/apideploysearchweirdness“itworkedlocally”CSChamp inthe devroomdogdeployvendorstatusincidentsomethinglive notwhat theyexpectedsomeonegroansloudly outof nowheresomeoneswearsout ofnowhereon-site folkmentionhow crazyit isOfflinedonationissueping indog-critical-issuesDonationsnotworkingsomeonegets acallsomethingnewcompletelybreaks

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