on-site folkmentionhow crazyit isstats“wrong”finding anewworkaroundslack calllongerthan 1hr@here or@channelCSChamp inthe devroommajorincident inoff hoursA sitegoesdowncustomerloveunrelated toatxsomeonegets acallPM inthe devroom“we’realmostthere”StatsnotupdatingsomethingnewcompletelybreaksvendorstatusincidentsearchweirdnessfeedramaDonationsnotworking“itworkedlocally”“whatcould gowrong?”somethinglive notwhat theyexpectedmaybeit’scaching?web/apideploydogdeployping indog-critical-issueson-sitefolk bragaboutfoodleaderboards“wrong”someoneswearsout ofnowherecustomerloverelated to atx> 3people atonecomputeroffice coldenoughfor coatsp2pissuessomeonegroansloudly outof nowhereping pongball rollsinto devrooman old bugresurfaces“we’relookinginto this”busfundissuesOfflinedonationissueleaderboardoutageson-site folkmentionhow crazyit isstats“wrong”finding anewworkaroundslack calllongerthan 1hr@here or@channelCSChamp inthe devroommajorincident inoff hoursA sitegoesdowncustomerloveunrelated toatxsomeonegets acallPM inthe devroom“we’realmostthere”StatsnotupdatingsomethingnewcompletelybreaksvendorstatusincidentsearchweirdnessfeedramaDonationsnotworking“itworkedlocally”“whatcould gowrong?”somethinglive notwhat theyexpectedmaybeit’scaching?web/apideploydogdeployping indog-critical-issueson-sitefolk bragaboutfoodleaderboards“wrong”someoneswearsout ofnowherecustomerloverelated to atx> 3people atonecomputeroffice coldenoughfor coatsp2pissuessomeonegroansloudly outof nowhereping pongball rollsinto devrooman old bugresurfaces“we’relookinginto this”busfundissuesOfflinedonationissueleaderboardoutages

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