(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
No female software engineers from Menlo
We need to explain how docker works to Menlo
We get asked a question that should be for instrument teams
SDC is blamed for a missing CAVA feature
SDC is asked to do some L3 work
More than 2 people from Menlo quit before Jan
Maintenance question isn't answered by Feb
Menlo asks for AWS accounts
Menlo actually gets weekly meetings
SDC is still missing L1 algorithms by Dec
Menlo breaks repo rules and never fixes them
One week sprint causes problems
File naming convention changes
Someone external breaks infra
SDC is asked
to fly out to Menlo
IMAP Comms team conflates Menlo and LASP
Missing inputs is a big issue if it's from the SDC
Someone implies SDC work is unimportant
Menlo copies our code without credit
Software versioning changes
Dependency changes post-Jan
SDC gets blamed for missing info we asked for
Menlo takes credit for an SDC feature
Multiple instrument
teams
complain to us about Menlo
