Hope fixestechnicaldifficulties inthe middle ofthe meetngTuscon doesn’tlet Centennialinto the Zoombefore themeeting starts“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Presenterreusesold slidesHyperfixateson a supernicheconceptSomeonestrugglesto log in toa systemRelativelinenumbersin vimAaron forgetsto show up formeeting/showsup lateTuscon hassideconversationsover thepresenterSomeone inCentennialtakes over andexplainsconceptquicker/betterSomeonefromChantilyspeaksSimulation(s) arementioned/discussedSomeonerantsaboutXMidasSomeonehas a freshdrink for themeeting“Hey, canyou guyshear usOK?”Codedoesn’trun/workPresentersays theycreatedslides day ofFPGA(s) arementioned/discussedSomeone inCentennialfalls asleepduringmeetingTusconintroducestheir newhires, but notCentennial’sGain/loss testing ismentioned/discussedCable testing ismentioned/discussedSlide is atleast 80%wordsTuscon asks aleadingquestion just sothey cananswer itthemselvesSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomOWL tracksa randomperson whois notspeakingField testing ismentioned/discussedSpencerattendsbecause hewants a breakfrom workCodeworks/runson firstattemptSDR(s) arementioned/discussedUsesvimUses emacs,notepad, orother text editor(not VSCode orother IDE)Calibration ismentioned/discussedFree!Horriblevim colorschemeTusconforgets tounmutetheir audioHardware-in-the-loopismentioned/discussedMeetingruns longerthan 1 hourSomeonealmostfalls out oftheir chairHope fixestechnicaldifficulties inthe middle ofthe meetngTuscon doesn’tlet Centennialinto the Zoombefore themeeting starts“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Presenterreusesold slidesHyperfixateson a supernicheconceptSomeonestrugglesto log in toa systemRelativelinenumbersin vimAaron forgetsto show up formeeting/showsup lateTuscon hassideconversationsover thepresenterSomeone inCentennialtakes over andexplainsconceptquicker/betterSomeonefromChantilyspeaksSimulation(s) arementioned/discussedSomeonerantsaboutXMidasSomeonehas a freshdrink for themeeting“Hey, canyou guyshear usOK?”Codedoesn’trun/workPresentersays theycreatedslides day ofFPGA(s) arementioned/discussedSomeone inCentennialfalls asleepduringmeetingTusconintroducestheir newhires, but notCentennial’sGain/loss testing ismentioned/discussedCable testing ismentioned/discussedSlide is atleast 80%wordsTuscon asks aleadingquestion just sothey cananswer itthemselvesSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomOWL tracksa randomperson whois notspeakingField testing ismentioned/discussedSpencerattendsbecause hewants a breakfrom workCodeworks/runson firstattemptSDR(s) arementioned/discussedUsesvimUses emacs,notepad, orother text editor(not VSCode orother IDE)Calibration ismentioned/discussedFree!Horriblevim colorschemeTusconforgets tounmutetheir audioHardware-in-the-loopismentioned/discussedMeetingruns longerthan 1 hourSomeonealmostfalls out oftheir chair

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