Presenterreusesold slidesSomeone inCentennialfalls asleepduringmeetingHorriblevim colorschemeField testing ismentioned/discussedPresentersays theycreatedslides day ofSomeonefromChantilyspeaksSomeonerantsaboutXMidasSDR(s) arementioned/discussedSimulation(s) arementioned/discussedSomeone inCentennialtakes over andexplainsconceptquicker/betterSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomHyperfixateson a supernicheconceptMeetingruns longerthan 1 hourUses emacs,notepad, orother text editor(not VSCode orother IDE)“Hey, canyou guyshear usOK?”“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Cable testing ismentioned/discussedCodedoesn’trun/workFree!Hardware-in-the-loopismentioned/discussedHope fixestechnicaldifficulties inthe middle ofthe meetngTusconintroducestheir newhires, but notCentennial’sSomeonestrugglesto log in toa systemSomeonehas a freshdrink for themeetingOWL tracksa randomperson whois notspeakingTusconforgets tounmutetheir audioSpencerattendsbecause hewants a breakfrom workSomeonealmostfalls out oftheir chairRelativelinenumbersin vimTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsCodeworks/runson firstattemptSlide is atleast 80%wordsUsesvimGain/loss testing ismentioned/discussedAaron forgetsto show up formeeting/showsup lateTuscon asks aleadingquestion just sothey cananswer itthemselvesCalibration ismentioned/discussedFPGA(s) arementioned/discussedTuscon hassideconversationsover thepresenterPresenterreusesold slidesSomeone inCentennialfalls asleepduringmeetingHorriblevim colorschemeField testing ismentioned/discussedPresentersays theycreatedslides day ofSomeonefromChantilyspeaksSomeonerantsaboutXMidasSDR(s) arementioned/discussedSimulation(s) arementioned/discussedSomeone inCentennialtakes over andexplainsconceptquicker/betterSomeone inTuscon asks aquestion thatisn’t repeatedfor ZoomHyperfixateson a supernicheconceptMeetingruns longerthan 1 hourUses emacs,notepad, orother text editor(not VSCode orother IDE)“Hey, canyou guyshear usOK?”“So I didn’tmake slidestoday, I thoughtwe’d just do ademonstrationinstead”Cable testing ismentioned/discussedCodedoesn’trun/workFree!Hardware-in-the-loopismentioned/discussedHope fixestechnicaldifficulties inthe middle ofthe meetngTusconintroducestheir newhires, but notCentennial’sSomeonestrugglesto log in toa systemSomeonehas a freshdrink for themeetingOWL tracksa randomperson whois notspeakingTusconforgets tounmutetheir audioSpencerattendsbecause hewants a breakfrom workSomeonealmostfalls out oftheir chairRelativelinenumbersin vimTuscon doesn’tlet Centennialinto the Zoombefore themeeting startsCodeworks/runson firstattemptSlide is atleast 80%wordsUsesvimGain/loss testing ismentioned/discussedAaron forgetsto show up formeeting/showsup lateTuscon asks aleadingquestion just sothey cananswer itthemselvesCalibration ismentioned/discussedFPGA(s) arementioned/discussedTuscon hassideconversationsover thepresenter

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