an old bugresurfacesstats“wrong”leaderboardoutages@here or@channelslack calllongerthan 1hrvendorstatusincidentoffice coldenoughfor coatssomethinglive notwhat theyexpectedsomeonegets acall> 3people atonecomputercustomerloverelated to atxbusfundissuescustomerloveunrelated toatxStatsnotupdatingfinding anewworkaroundon-site folkmentionhow crazyit isDonationsnotworkingsomethingnewcompletelybreaksdogdeployOfflinedonationissue“whatcould gowrong?”A sitegoesdownon-sitefolk bragaboutfoodmaybeit’scaching?ping pongball rollsinto devroomsomeoneswearsout ofnowhereping indog-critical-issuesweb/apideployp2pissuesleaderboards“wrong”PM inthe devroom“we’relookinginto this”feedramaCSChamp inthe devroom“itworkedlocally”“we’realmostthere”searchweirdnessmajorincident inoff hourssomeonegroansloudly outof nowherean old bugresurfacesstats“wrong”leaderboardoutages@here or@channelslack calllongerthan 1hrvendorstatusincidentoffice coldenoughfor coatssomethinglive notwhat theyexpectedsomeonegets acall> 3people atonecomputercustomerloverelated to atxbusfundissuescustomerloveunrelated toatxStatsnotupdatingfinding anewworkaroundon-site folkmentionhow crazyit isDonationsnotworkingsomethingnewcompletelybreaksdogdeployOfflinedonationissue“whatcould gowrong?”A sitegoesdownon-sitefolk bragaboutfoodmaybeit’scaching?ping pongball rollsinto devroomsomeoneswearsout ofnowhereping indog-critical-issuesweb/apideployp2pissuesleaderboards“wrong”PM inthe devroom“we’relookinginto this”feedramaCSChamp inthe devroom“itworkedlocally”“we’realmostthere”searchweirdnessmajorincident inoff hourssomeonegroansloudly outof nowhere

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