somethinglive notwhat theyexpectedleaderboards“wrong”an old bugresurfacesfinding anewworkaroundStatsnotupdatingPM inthe devroom“we’relookinginto this”office coldenoughfor coatsweb/apideployon-site folkmentionhow crazyit isleaderboardoutagesmajorincident inoff hours@here or@channelCSChamp inthe devroombusfundissuessomeonegets acallcustomerloveunrelated toatxstats“wrong”Donationsnotworkingcustomerloverelated to atxA sitegoesdownsomeonegroansloudly outof nowhere“itworkedlocally”on-sitefolk bragaboutfoodfeedramavendorstatusincidentmaybeit’scaching?Offlinedonationissuesomethingnewcompletelybreakssomeoneswearsout ofnowhereslack calllongerthan 1hr“whatcould gowrong?”ping pongball rollsinto devroomdogdeploy> 3people atonecomputer“we’realmostthere”searchweirdnessping indog-critical-issuesp2pissuessomethinglive notwhat theyexpectedleaderboards“wrong”an old bugresurfacesfinding anewworkaroundStatsnotupdatingPM inthe devroom“we’relookinginto this”office coldenoughfor coatsweb/apideployon-site folkmentionhow crazyit isleaderboardoutagesmajorincident inoff hours@here or@channelCSChamp inthe devroombusfundissuessomeonegets acallcustomerloveunrelated toatxstats“wrong”Donationsnotworkingcustomerloverelated to atxA sitegoesdownsomeonegroansloudly outof nowhere“itworkedlocally”on-sitefolk bragaboutfoodfeedramavendorstatusincidentmaybeit’scaching?Offlinedonationissuesomethingnewcompletelybreakssomeoneswearsout ofnowhereslack calllongerthan 1hr“whatcould gowrong?”ping pongball rollsinto devroomdogdeploy> 3people atonecomputer“we’realmostthere”searchweirdnessping indog-critical-issuesp2pissues

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