“Hey, canyou guyshear usOK?”Someone inCentennialtakes over andexplainsconceptquicker/betterRelativelinenumbersin vimHope fixestechnicaldifficulties inthe middle ofthe meetngSDR(s) arementioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselves“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Spencerattendsbecause hewants a breakfrom workUsesvimSlide is atleast 80%wordsTuscon hassideconversationsover thepresenterSomeonestrugglesto log in toa systemHyperfixateson a supernicheconceptSomeonerantsaboutXMidasSimulation(s) arementioned/discussedFPGA(s) arementioned/discussedSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomTusconintroducestheir newhires, but notCentennial’sAaron forgetsto show up formeeting/showsup lateSomeonefromChantilyspeaksUses emacs,notepad, orother text editor(not VSCode orother IDE)Tusconforgets tounmutetheir audioHardware-in-the-loopismentioned/discussedFree!Someonealmostfalls out oftheir chairSomeonehas a freshdrink for themeetingCodeworks/runson firstattemptPresentersays theycreatedslides day ofTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsField testing ismentioned/discussedGain/loss testing ismentioned/discussedMeetingruns longerthan 1 hourHorriblevim colorschemePresenterreusesold slidesCalibration ismentioned/discussedCodedoesn’trun/workSomeone inCentennialfalls asleepduringmeetingCable testing ismentioned/discussedOWL tracksa randomperson whois notspeaking“Hey, canyou guyshear usOK?”Someone inCentennialtakes over andexplainsconceptquicker/betterRelativelinenumbersin vimHope fixestechnicaldifficulties inthe middle ofthe meetngSDR(s) arementioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselves“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Spencerattendsbecause hewants a breakfrom workUsesvimSlide is atleast 80%wordsTuscon hassideconversationsover thepresenterSomeonestrugglesto log in toa systemHyperfixateson a supernicheconceptSomeonerantsaboutXMidasSimulation(s) arementioned/discussedFPGA(s) arementioned/discussedSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomTusconintroducestheir newhires, but notCentennial’sAaron forgetsto show up formeeting/showsup lateSomeonefromChantilyspeaksUses emacs,notepad, orother text editor(not VSCode orother IDE)Tusconforgets tounmutetheir audioHardware-in-the-loopismentioned/discussedFree!Someonealmostfalls out oftheir chairSomeonehas a freshdrink for themeetingCodeworks/runson firstattemptPresentersays theycreatedslides day ofTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsField testing ismentioned/discussedGain/loss testing ismentioned/discussedMeetingruns longerthan 1 hourHorriblevim colorschemePresenterreusesold slidesCalibration ismentioned/discussedCodedoesn’trun/workSomeone inCentennialfalls asleepduringmeetingCable testing ismentioned/discussedOWL tracksa randomperson whois notspeaking

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