(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
you wake up to 20+ unread in the PDS slack channel
"the issue is now gone but we would like to know the root cause"
disabling email notifs on a newly logged-in stack
wanting to do something absolutely degenerate in Code Workspaces
"any updates?" within 4 hours of filing
Code Workbook environment won't initialize
"Give me an API endpoint that does exactly what I want"
automation sends you the wrong type of ticket
"I want to implement a cyclical dependency on purpose"
incessant followups on a very specific FR that only benefits them
user puts all issue information in a Word or Powerpoint file for some reason
OOM on Sonic and they don't want to run a build to test
talking about their internal data and infra as if we know what they're saying
Literally asking you to write code for them
"please treat this with priority" but it's a non-blocking FE bug
Permissions issue but the logs show no indication of this
begging to hop on a call for no reason
wondering why their convoluted hacky workflow they came up with doesn't work
providing links on a zero-access stack when they should know this by now
screenshot of AIP explainer instead of a copy of the actual logs
"schedule unexpectedly starting build"
IMPL flags a ticket with 14hr SLI to you bc the users won't stop pestering them
Ticket is about a part of the platform you didn't even know existed
repo upgrade issue but the repo is so old it has transforms-mesa in it
