Aaron forgetsto show up formeeting/showsup lateCalibration ismentioned/discussed“Hey, canyou guyshear usOK?”Someonehas a freshdrink for themeetingPresentersays theycreatedslides day ofSomeonefromChantilyspeaksSomeone inCentennialfalls asleepduringmeetingCodeworks/runson firstattemptPresenterreusesold slidesGain/loss testing ismentioned/discussedHope fixestechnicaldifficulties inthe middle ofthe meetngHorriblevim colorschemeUsesvimSDR(s) arementioned/discussedSomeonestrugglesto log in toa systemFree!FPGA(s) arementioned/discussed“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Slide is atleast 80%wordsSomeonerantsaboutXMidasTuscon asks aleadingquestion just sothey cananswer itthemselvesOWL tracksa randomperson whois notspeakingUses emacs,notepad, orother text editor(not VSCode orother IDE)Spencerattendsbecause hewants a breakfrom workTusconintroducestheir newhires, but notCentennial’sSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomField testing ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsCable testing ismentioned/discussedTuscon hassideconversationsover thepresenterSomeone inCentennialtakes over andexplainsconceptquicker/betterCodedoesn’trun/workSomeonealmostfalls out oftheir chairMeetingruns longerthan 1 hourSimulation(s) arementioned/discussedHyperfixateson a supernicheconceptTusconforgets tounmutetheir audioHardware-in-the-loopismentioned/discussedRelativelinenumbersin vimAaron forgetsto show up formeeting/showsup lateCalibration ismentioned/discussed“Hey, canyou guyshear usOK?”Someonehas a freshdrink for themeetingPresentersays theycreatedslides day ofSomeonefromChantilyspeaksSomeone inCentennialfalls asleepduringmeetingCodeworks/runson firstattemptPresenterreusesold slidesGain/loss testing ismentioned/discussedHope fixestechnicaldifficulties inthe middle ofthe meetngHorriblevim colorschemeUsesvimSDR(s) arementioned/discussedSomeonestrugglesto log in toa systemFree!FPGA(s) arementioned/discussed“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Slide is atleast 80%wordsSomeonerantsaboutXMidasTuscon asks aleadingquestion just sothey cananswer itthemselvesOWL tracksa randomperson whois notspeakingUses emacs,notepad, orother text editor(not VSCode orother IDE)Spencerattendsbecause hewants a breakfrom workTusconintroducestheir newhires, but notCentennial’sSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomField testing ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsCable testing ismentioned/discussedTuscon hassideconversationsover thepresenterSomeone inCentennialtakes over andexplainsconceptquicker/betterCodedoesn’trun/workSomeonealmostfalls out oftheir chairMeetingruns longerthan 1 hourSimulation(s) arementioned/discussedHyperfixateson a supernicheconceptTusconforgets tounmutetheir audioHardware-in-the-loopismentioned/discussedRelativelinenumbersin vim

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