OWL tracksa randomperson whois notspeakingFPGA(s) arementioned/discussedHope fixestechnicaldifficulties inthe middle ofthe meetngTusconforgets tounmutetheir audioRelativelinenumbersin vimSpencerattendsbecause hewants a breakfrom workCalibration ismentioned/discussedTusconintroducestheir newhires, but notCentennial’sTuscon hassideconversationsover thepresenterSlide is atleast 80%wordsFree!SomeonerantsaboutXMidasSomeonestrugglesto log in toa systemSomeonefromChantilyspeaksPresentersays theycreatedslides day ofSimulation(s) arementioned/discussedCodedoesn’trun/workField testing ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsHorriblevim colorschemeSDR(s) arementioned/discussed“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Someone inCentennialtakes over andexplainsconceptquicker/betterCodeworks/runson firstattemptHardware-in-the-loopismentioned/discussedSomeonealmostfalls out oftheir chairGain/loss testing ismentioned/discussedUses emacs,notepad, orother text editor(not VSCode orother IDE)Someone inCentennialfalls asleepduringmeetingTuscon asks aleadingquestion just sothey cananswer itthemselvesUsesvim“Hey, canyou guyshear usOK?”Meetingruns longerthan 1 hourHyperfixateson a supernicheconceptCable testing ismentioned/discussedSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSomeonehas a freshdrink for themeetingAaron forgetsto show up formeeting/showsup latePresenterreusesold slidesOWL tracksa randomperson whois notspeakingFPGA(s) arementioned/discussedHope fixestechnicaldifficulties inthe middle ofthe meetngTusconforgets tounmutetheir audioRelativelinenumbersin vimSpencerattendsbecause hewants a breakfrom workCalibration ismentioned/discussedTusconintroducestheir newhires, but notCentennial’sTuscon hassideconversationsover thepresenterSlide is atleast 80%wordsFree!SomeonerantsaboutXMidasSomeonestrugglesto log in toa systemSomeonefromChantilyspeaksPresentersays theycreatedslides day ofSimulation(s) arementioned/discussedCodedoesn’trun/workField testing ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsHorriblevim colorschemeSDR(s) arementioned/discussed“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Someone inCentennialtakes over andexplainsconceptquicker/betterCodeworks/runson firstattemptHardware-in-the-loopismentioned/discussedSomeonealmostfalls out oftheir chairGain/loss testing ismentioned/discussedUses emacs,notepad, orother text editor(not VSCode orother IDE)Someone inCentennialfalls asleepduringmeetingTuscon asks aleadingquestion just sothey cananswer itthemselvesUsesvim“Hey, canyou guyshear usOK?”Meetingruns longerthan 1 hourHyperfixateson a supernicheconceptCable testing ismentioned/discussedSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSomeonehas a freshdrink for themeetingAaron forgetsto show up formeeting/showsup latePresenterreusesold slides

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