Aaron forgetsto show up formeeting/showsup lateCable testing ismentioned/discussedMeetingruns longerthan 1 hourSDR(s) arementioned/discussedCalibration ismentioned/discussedPresentersays theycreatedslides day ofTuscon hassideconversationsover thepresenterRelativelinenumbersin vimCodeworks/runson firstattemptHardware-in-the-loopismentioned/discussedSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSpencerattendsbecause hewants a breakfrom workSomeonerantsaboutXMidasUsesvimCodedoesn’trun/workOWL tracksa randomperson whois notspeakingTuscon asks aleadingquestion just sothey cananswer itthemselvesSomeonestrugglesto log in toa systemSomeonefromChantilyspeaksUses emacs,notepad, orother text editor(not VSCode orother IDE)Slide is atleast 80%wordsSimulation(s) arementioned/discussedFree!Tusconintroducestheir newhires, but notCentennial’s“Hey, canyou guyshear usOK?”Someonehas a freshdrink for themeetingPresenterreusesold slidesTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsHorriblevim colorschemeHope fixestechnicaldifficulties inthe middle ofthe meetngSomeonealmostfalls out oftheir chair“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”FPGA(s) arementioned/discussedSomeone inCentennialtakes over andexplainsconceptquicker/betterGain/loss testing ismentioned/discussedField testing ismentioned/discussedSomeone inCentennialfalls asleepduringmeetingHyperfixateson a supernicheconceptTusconforgets tounmutetheir audioAaron forgetsto show up formeeting/showsup lateCable testing ismentioned/discussedMeetingruns longerthan 1 hourSDR(s) arementioned/discussedCalibration ismentioned/discussedPresentersays theycreatedslides day ofTuscon hassideconversationsover thepresenterRelativelinenumbersin vimCodeworks/runson firstattemptHardware-in-the-loopismentioned/discussedSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomSpencerattendsbecause hewants a breakfrom workSomeonerantsaboutXMidasUsesvimCodedoesn’trun/workOWL tracksa randomperson whois notspeakingTuscon asks aleadingquestion just sothey cananswer itthemselvesSomeonestrugglesto log in toa systemSomeonefromChantilyspeaksUses emacs,notepad, orother text editor(not VSCode orother IDE)Slide is atleast 80%wordsSimulation(s) arementioned/discussedFree!Tusconintroducestheir newhires, but notCentennial’s“Hey, canyou guyshear usOK?”Someonehas a freshdrink for themeetingPresenterreusesold slidesTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsHorriblevim colorschemeHope fixestechnicaldifficulties inthe middle ofthe meetngSomeonealmostfalls out oftheir chair“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”FPGA(s) arementioned/discussedSomeone inCentennialtakes over andexplainsconceptquicker/betterGain/loss testing ismentioned/discussedField testing ismentioned/discussedSomeone inCentennialfalls asleepduringmeetingHyperfixateson a supernicheconceptTusconforgets tounmutetheir audio

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