(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
Tuscon doesn’t let Centennial into the Zoom before the meeting starts
Free!
Tuscon asks a leading question just so they can answer it themselves
Someone has a fresh drink for the meeting
FPGA(s) are mentioned/discussed
Spencer attends because he wants a break from work
Presenter reuses old slides
Slide is at least 80% words
SDR(s) are mentioned/discussed
Aaron forgets to show up for meeting/shows up late
Presenter says they created slides day of
“Hey, can you guys hear us OK?”
Gain/loss testing is mentioned/discussed
Tuscon has side conversations over the presenter
Code works/runs on first attempt
Field testing is mentioned/discussed
Someone almost falls out of their chair
Someone rants about XMidas
Uses vim
“So I didn’t make slides today, I thought we’d just do a demonstration instead”
Someone from Chantily speaks
Someone in Centennial takes over and explains concept quicker/better
Relative line numbers in vim
Someone in Centennial falls asleep during meeting
Tuscon forgets to unmute their audio
Uses emacs, notepad, or other text editor (not VSCode or other IDE)
Someone struggles to log in to a system
Horrible vim color scheme
Calibration is mentioned/discussed
Simulation(s) are mentioned/discussed
Hyperfixates on a super niche concept
Meeting runs longer than 1 hour
OWL tracks a random person who is not speaking
Tuscon introduces their new hires, but not Centennial’s
Hardware-in-the-loop is mentioned/discussed
Code doesn’t run/work
Someone in Tuscon asks a question that isn’t repeated for Zoom
Hope fixes technical difficulties in the middle of the meetng
