Cable testing ismentioned/discussedHardware-in-the-loopismentioned/discussedHorriblevim colorschemeFPGA(s) arementioned/discussedPresenterreusesold slides“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Field testing ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsRelativelinenumbersin vimMeetingruns longerthan 1 hourSomeonefromChantilyspeaksTuscon asks aleadingquestion just sothey cananswer itthemselvesSomeone inCentennialfalls asleepduringmeetingTuscon hassideconversationsover thepresenterSlide is atleast 80%wordsSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomHope fixestechnicaldifficulties inthe middle ofthe meetngSimulation(s) arementioned/discussedSDR(s) arementioned/discussedCodedoesn’trun/workUsesvimSomeonestrugglesto log in toa systemSomeonerantsaboutXMidasHyperfixateson a supernicheconceptFree!Tusconforgets tounmutetheir audioSomeone inCentennialtakes over andexplainsconceptquicker/betterAaron forgetsto show up formeeting/showsup lateGain/loss testing ismentioned/discussed“Hey, canyou guyshear usOK?”Codeworks/runson firstattemptPresentersays theycreatedslides day ofSomeonehas a freshdrink for themeetingOWL tracksa randomperson whois notspeakingTusconintroducestheir newhires, but notCentennial’sSpencerattendsbecause hewants a breakfrom workCalibration ismentioned/discussedSomeonealmostfalls out oftheir chairUses emacs,notepad, orother text editor(not VSCode orother IDE)Cable testing ismentioned/discussedHardware-in-the-loopismentioned/discussedHorriblevim colorschemeFPGA(s) arementioned/discussedPresenterreusesold slides“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Field testing ismentioned/discussedTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsRelativelinenumbersin vimMeetingruns longerthan 1 hourSomeonefromChantilyspeaksTuscon asks aleadingquestion just sothey cananswer itthemselvesSomeone inCentennialfalls asleepduringmeetingTuscon hassideconversationsover thepresenterSlide is atleast 80%wordsSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomHope fixestechnicaldifficulties inthe middle ofthe meetngSimulation(s) arementioned/discussedSDR(s) arementioned/discussedCodedoesn’trun/workUsesvimSomeonestrugglesto log in toa systemSomeonerantsaboutXMidasHyperfixateson a supernicheconceptFree!Tusconforgets tounmutetheir audioSomeone inCentennialtakes over andexplainsconceptquicker/betterAaron forgetsto show up formeeting/showsup lateGain/loss testing ismentioned/discussed“Hey, canyou guyshear usOK?”Codeworks/runson firstattemptPresentersays theycreatedslides day ofSomeonehas a freshdrink for themeetingOWL tracksa randomperson whois notspeakingTusconintroducestheir newhires, but notCentennial’sSpencerattendsbecause hewants a breakfrom workCalibration ismentioned/discussedSomeonealmostfalls out oftheir chairUses emacs,notepad, orother text editor(not VSCode orother IDE)

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