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