SomeonefromChantilyspeaksUsesvimSomeonehas a freshdrink for themeetingSomeonerantsaboutXMidasPresenterreusesold slidesSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSomeonealmostfalls out oftheir chairCodedoesn’trun/workHope fixestechnicaldifficulties inthe middle ofthe meetngOWL tracksa randomperson whois notspeakingTusconintroducestheir newhires, but notCentennial’sField testing ismentioned/discussedFPGA(s) arementioned/discussedPresentersays theycreatedslides day ofHyperfixateson a supernicheconceptHardware-in-the-loopismentioned/discussedUses emacs,notepad, orother text editor(not VSCode orother IDE)Meetingruns longerthan 1 hourCable testing ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsSomeone inCentennialfalls asleepduringmeetingSomeone inCentennialtakes over andexplainsconceptquicker/betterCalibration ismentioned/discussedFree!Slide is atleast 80%wordsCodeworks/runson firstattemptSDR(s) arementioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselvesTuscon hassideconversationsover thepresenterAaron forgetsto show up formeeting/showsup lateGain/loss testing ismentioned/discussed“Hey, canyou guyshear usOK?”Relativelinenumbersin vimHorriblevim colorscheme“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Simulation(s) arementioned/discussedSomeonestrugglesto log in toa systemTusconforgets tounmutetheir audioSpencerattendsbecause hewants a breakfrom workSomeonefromChantilyspeaksUsesvimSomeonehas a freshdrink for themeetingSomeonerantsaboutXMidasPresenterreusesold slidesSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSomeonealmostfalls out oftheir chairCodedoesn’trun/workHope fixestechnicaldifficulties inthe middle ofthe meetngOWL tracksa randomperson whois notspeakingTusconintroducestheir newhires, but notCentennial’sField testing ismentioned/discussedFPGA(s) arementioned/discussedPresentersays theycreatedslides day ofHyperfixateson a supernicheconceptHardware-in-the-loopismentioned/discussedUses emacs,notepad, orother text editor(not VSCode orother IDE)Meetingruns longerthan 1 hourCable testing ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsSomeone inCentennialfalls asleepduringmeetingSomeone inCentennialtakes over andexplainsconceptquicker/betterCalibration ismentioned/discussedFree!Slide is atleast 80%wordsCodeworks/runson firstattemptSDR(s) arementioned/discussedTuscon asks aleadingquestion just sothey cananswer itthemselvesTuscon hassideconversationsover thepresenterAaron forgetsto show up formeeting/showsup lateGain/loss testing ismentioned/discussed“Hey, canyou guyshear usOK?”Relativelinenumbersin vimHorriblevim colorscheme“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Simulation(s) arementioned/discussedSomeonestrugglesto log in toa systemTusconforgets tounmutetheir audioSpencerattendsbecause hewants a breakfrom work

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